On 12/06/2014, at 2:22 PM, Ravishankar N wrote: <snip> > But we will still hit the problem when rolling upgrade is performed > from 3.4 to 3.5, unless the clients are also upgraded to 3.5 Could we introduce a client side patch into (say) 3.4.5 that helps with this? Then mandate that 3.4 -> 3.5 rolling upgrades have to be on 3.4.5 first? 3.4.x -> 3.4.5 should be "no issues" yeah? + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
