Displaying 4 results from an estimated 4 matches for "yongtw123".
2017 Aug 25
2
Rolling upgrade from 3.6.3 to 3.10.5
...il.com> wrote:
> I was never able to go from 3.6.x to 3.7.x without downtime. Then
> 3.7.x did not work well for me, so I stuck with 3.6.x until recently.
> I went from 3.6.x to 3.10.x but downtime was scheduled.
>
> Diego
>
> On Fri, Aug 25, 2017 at 8:25 AM, Yong Tseng <yongtw123 at gmail.com> wrote:
> > Hi Diego,
> >
> > Thanks for the information. I tried only setting 'allow-insecure on' but
> > nada.
> > The sentence "If you are using GlusterFS version 3.4.x or below, you can
> > upgrade it to following" in documen...
2017 Aug 25
0
Rolling upgrade from 3.6.3 to 3.10.5
...make sure
all was OK (Not all was OK for me, but that may be a samba issue as I
use it as a file server).
6. Upgraded the op version to maximum available.
In my case, I have two servers with bricks and one server that acts as
a witness.
HTH,
Diego
On Fri, Aug 25, 2017 at 8:56 AM, Yong Tseng <yongtw123 at gmail.com> wrote:
> Hi Diego,
>
> Just to clarify, so did you do an offline upgrade with an existing cluster
> (3.6.x => 3.10.x)?
> Thanks.
>
> On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote:
>>
>> I was never able to go...
2017 Aug 25
0
Rolling upgrade from 3.6.3 to 3.10.5
....allow-insecure on Edit
/etc/glusterfs/glusterd.vol to contain this line: option
rpc-auth-allow-insecure on
Post 1, restarting the volume would be necessary:
# gluster volume stop <volname>
# gluster volume start <volname>
HTH,
Diego
On Fri, Aug 25, 2017 at 7:46 AM, Yong Tseng <yongtw123 at gmail.com> wrote:
> Hi all,
>
> I'm currently in process of upgrading a replicated cluster (1 x 4) from
> 3.6.3 to 3.10.5. The nodes run CentOS 6. However after upgrading the first
> node, the said node fails to connect to other peers (as seen via 'gluster
> peer sta...
2017 Aug 25
2
Rolling upgrade from 3.6.3 to 3.10.5
Hi all,
I'm currently in process of upgrading a replicated cluster (1 x 4) from
3.6.3 to 3.10.5. The nodes run CentOS 6. However after upgrading the first
node, the said node fails to connect to other peers (as seen via 'gluster
peer status'), but somehow other non-upgraded peers can still see the
upgraded peer as connected.
Writes to the Gluster volume via local mounts of