I've done just this in our integration environment and our production environment. I halted my application on the first server, unmounted the filesystem, halted glusterfsd, upgraded it, restarted glustersfd and mounted the filesystem. I checked that read/writes were fine and then brought it back into service. I left this for 24 hours, then repeated the process on the secondary node. You shouldn't have any problems. -- joe. -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Steve Wilson Sent: 21 July 2010 17:22 To: gluster-users at gluster.org Subject: Upgrading from 3.0.4 to 3.0.5 I am planning to upgrade a Gluster installation from 3.0.4 to 3.0.5. Can I do so in a piecemeal manner without taking the volume out of service? In other words, can I bring down one replication server, upgrade it, and bring it up again while the other servers are running? Also, will 3.0.4 clients work with 3.0.5 servers and vice-versa? If so, then it sounds like I could slide in the upgrade without major disruption of service. Thanks, Steve _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
