That seems excessive. If you have a replicated volume you should be able to
just unmount, upgrade, and mount each client. Then, after checking heal info to
ensure there are no heals pending, upgrade one server at a time. Check heal
info between each server upgrade.
On April 27, 2015 6:24:32 PM PDT, Atin Mukherjee <[email protected]> wrote:
>
>
>On 04/28/2015 06:53 AM, Atin Mukherjee wrote:
>>
>>
>> On 04/28/2015 06:37 AM, 何亦军 wrote:
>>> Hi Guys,
>>>
>>> How to upgrade GlusterFS to 3.6.3 from 3.6.2 ? Any
>document talk about that?
>>
>http://www.gluster.org/community/documentation/index.php/Upgrade_to_3.6
>> talks about how to upgrade from 3.4/3.5 to 3.6, however you could
>follow
>> the same steps like:
>>
>> Scheduling a downtime (Recommended)
>>
>> For this approach, schedule a downtime and prevent all your clients
>from
>> accessing ( umount your volumes, stop gluster Volumes..etc)the
>servers.
>>
>> 1. Stop all glusterd, glusterfsd and glusterfs processes on your
>server.
>> 2. Install GlusterFS 3.6.0
>Read it as install GlusterFS 3.6.3
>> 3. Start glusterd.
>> 4. Ensure that all started volumes have processes online in
>“gluster
>> volume status”.
>>
>>
>> You would need to repeat these steps on all servers that form your
>> trusted storage pool.
>>
>> After upgrading the servers, it is recommended to upgrade all client
>> installations to 3.6.0
>>
>> HTH,
>> Atin
>>>
>>>
>>>
>>> _______________________________________________
>>> Gluster-users mailing list
>>> [email protected]
>>> http://www.gluster.org/mailman/listinfo/gluster-users
>>>
>>
>
>--
>~Atin
>_______________________________________________
>Gluster-users mailing list
>[email protected]
>http://www.gluster.org/mailman/listinfo/gluster-users
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
