[Gluster-devel] Upgrading Gluster
u2sashko at gmail.com
Wed Dec 9 16:48:25 UTC 2009
Anand, how stable is 3.0 right now? Would you advise to go with 2.0.8 or 3.0
on a production environment? I've been running 2.0.4 and wanted to upgrade
to 2.0.8 but figured if I'm going through the hassle, I could go to 3.0.
Only if it's as stable though.
On Wed, Dec 9, 2009 at 4:14 AM, Anand Babu Periasamy <ab at gluster.com> wrote:
> Brian Hirt wrote:
>> I have a question about upgrading, but it's not really answered in
>> I have a 4 node system, with AFR/Distribute. Can I shut down the servers
>> one at a time, upgrade from 2.0.6 to 2.0.8 and restart the node. After
>> doing this process on all four servers will everything be running okay?
>> Also, a bit longer term, migrating from 2.x to the soon to be released 3.x
>> branch, will this method work as well? Once all servers have been upgraded,
>> will they automatically renegotiate to the most recent protocol or does the
>> entire cluster need to be shut down and restarted.
> Hi Brian,
> You can do that between 2.0.6 to 2.0.8. All 2.0.x will be compatible to
> each other. Though I recommend upgrading all servers at once. To upgrade to
> 3, you need to upgrade all your servers and clients. Backend data layout is
> same. After upgrading the installation, you restart GlusterFS servers and
> remount the clients.
> Dynamic volume management (to add, remove, suspend) servers without
> requiring re-mount is going to be the key focus of 3.1 release.
> Anand Babu Periasamy
> GPG Key ID: 0x62E15A31
> Blog [http://unlocksmith.org]
> Twitter [http://twitter.com/unlocksmith]
> GNU/Linux [http://www.gnu.org]
> GlusterFS [http://www.gluster.org]
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel