On 06/12/2014 11:09 PM, Ravishankar N wrote:
On 06/12/2014 08:19 PM, Justin Clift wrote:
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?
But the client side patch is needed only if Avati's server (posix) fix
is present. And that is present only in 3.5 and not 3.4 .
Then mandate that 3.4 -> 3.5 rolling upgrades have to be on 3.4.5
first?
The idea of a rolling upgrade is that customers don't have to stop
their (hundreds of ?) clients from accessing the gluster volume and
the replica configuration ensures HA during rolling upgrade of
servers. When the can afford downtime of their application, then they
stop the clients and upgrade them as well. So the rolling upgrade
solution has to be independent of client side features.
3.4.x -> 3.4.5 should be "no issues" yeah?
After the fix on the server side i.e. posix xlator, no issue.
Pranith
+ 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
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
