2-shchst01
>>> brick-9=shchhv02-sto:-data-brick4-shchst01
>>> brick-10=shchhv03-sto:-data-brick4-shchst01
>>> brick-11=shchhv04-sto:-data-brick4-shchst01
>>>
>>> Another Server: shchhv02-sto
>>> ==========
>>> type=2
>&
> snap-max-hard-limit=256
>> cluster.data-self-heal-algorithm=full
>> features.shard-block-size=512MB
>> features.shard=enable
>> performance.readdir-ahead=on
>> storage.owner-uid=9869
>> storage.owner-gid=9869
>> server.allow-insecure=on
>> perfor
brick-9=shchhv02-sto:-data-brick4-shchst01
> brick-10=shchhv03-sto:-data-brick4-shchst01
> brick-11=shchhv04-sto:-data-brick4-shchst01
>
> NOTE
>
> [root@shchhv01 shchst01]# gluster volume get shchst01 cluster.op-version
> Warning: Support to get global option value using
cluster.op-version 30800
-Original Message-
From: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] On Behalf Of Ziemowit Pierzycki
Sent: Tuesday, December 19, 2017 3:56 PM
To: gluster-users <gluster-users@gluster.org>
Subject: Re: [Gluster-users
I have not done the upgrade yet. Since this is a production cluster I
need to make sure it stays up or schedule some downtime if it doesn't
doesn't. Thanks.
On Tue, Dec 19, 2017 at 10:11 AM, Atin Mukherjee wrote:
>
>
> On Tue, Dec 19, 2017 at 1:10 AM, Ziemowit Pierzycki
On Tue, Dec 19, 2017 at 1:10 AM, Ziemowit Pierzycki
wrote:
> Hi,
>
> I have a cluster of 10 servers all running Fedora 24 along with
> Gluster 3.8. I'm planning on doing rolling upgrades to Fedora 27 with
> Gluster 3.12. I saw the documentation and did some testing but
Hi,
I have a cluster of 10 servers all running Fedora 24 along with
Gluster 3.8. I'm planning on doing rolling upgrades to Fedora 27 with
Gluster 3.12. I saw the documentation and did some testing but I
would like to run my plan through some (more?) educated minds.
The current setup is: