Gluster users - Aug 2020 - Upgrade from 6.9 to 7.7 stuck (peer is rejected)

Hello,

I just started an upgrade of my 3 nodes replica (incl arbiter) of GlusterFS from
6.9 to 7.7 but unfortunately after upgrading the first node, that node gets
rejected due to the following error:

[2020-08-22 17:43:00.240990] E [MSGID: 106012]
[glusterd-utils.c:3537:glusterd_compare_friend_volume] 0-management: Cksums of
quota configuration of volume myvolume differ. local cksum = 3013120651, remote 
cksum = 0 on peer myfirstnode.domain.tld

So glusterd process is running but not glusterfsd.

I am exactly in the same issue as described here:

https://www.gitmemory.com/Adam2Marsh

But I do not see any solutions or workaround. So now I am stuck with a degraded
GlusterFS cluster.

Could someone please advise me as soon as possible on what I should do? Is there
maybe any workarounds?

Thank you very much in advance for your response.

Best regards,
Mabi

Hello,

So to be precise I am exactly having the following issue:

https://github.com/gluster/glusterfs/issues/1332

I could not wait any longer to find some workarounds or quick fixes so I decided
to downgrade my rejected from 7.7 back to 6.9 which worked.

I would be really glad if someone could fix this issue or provide me a
workaround which works because version 6 of GlusterFS is not supported anymore
so I would really like to move on to the stable version 7.

Thank you very much in advance.

Best regards,
Mabi


??????? Original Message ???????
On Saturday, August 22, 2020 7:53 PM, mabi <mabi at protonmail.ch> wrote:
> Hello,
>
> I just started an upgrade of my 3 nodes replica (incl arbiter) of GlusterFS
from 6.9 to 7.7 but unfortunately after upgrading the first node, that node gets
rejected due to the following error:
>
> [2020-08-22 17:43:00.240990] E [MSGID: 106012]
[glusterd-utils.c:3537:glusterd_compare_friend_volume] 0-management: Cksums of
quota configuration of volume myvolume differ. local cksum = 3013120651, remote
cksum = 0 on peer myfirstnode.domain.tld
>
> So glusterd process is running but not glusterfsd.
>
> I am exactly in the same issue as described here:
>
> https://www.gitmemory.com/Adam2Marsh
>
> But I do not see any solutions or workaround. So now I am stuck with a
degraded GlusterFS cluster.
>
> Could someone please advise me as soon as possible on what I should do? Is
there maybe any workarounds?
>
> Thank you very much in advance for your response.
>
> Best regards,
> Mabi

Your e-mail got in the spam...?

If you haven't fixed the issue, check Hari's topic about quota issues
(based on the error message you provided)
:?https://medium.com/@harigowtham/glusterfs-quota-fix-accounting-840df33fcd3a

Most probably there is a quota issue and you need to fix it.

Best Regards,
Strahil Nikolov






? ??????, 23 ?????? 2020 ?., 11:05:27 ???????+3, mabi <mabi at
protonmail.ch> ??????:





Hello,

So to be precise I am exactly having the following issue:

https://github.com/gluster/glusterfs/issues/1332

I could not wait any longer to find some workarounds or quick fixes so I decided
to downgrade my rejected from 7.7 back to 6.9 which worked.

I would be really glad if someone could fix this issue or provide me a
workaround which works because version 6 of GlusterFS is not supported anymore
so I would really like to move on to the stable version 7.

Thank you very much in advance.

Best regards,
Mabi


??????? Original Message ???????

On Saturday, August 22, 2020 7:53 PM, mabi <mabi at protonmail.ch> wrote:
> Hello,
>
> I just started an upgrade of my 3 nodes replica (incl arbiter) of GlusterFS
from 6.9 to 7.7 but unfortunately after upgrading the first node, that node gets
rejected due to the following error:
>
> [2020-08-22 17:43:00.240990] E [MSGID: 106012]
[glusterd-utils.c:3537:glusterd_compare_friend_volume] 0-management: Cksums of
quota configuration of volume myvolume differ. local cksum = 3013120651, remote
cksum = 0 on peer myfirstnode.domain.tld
>
> So glusterd process is running but not glusterfsd.
>
> I am exactly in the same issue as described here:
>
> https://www.gitmemory.com/Adam2Marsh
>
> But I do not see any solutions or workaround. So now I am stuck with a
degraded GlusterFS cluster.
>
> Could someone please advise me as soon as possible on what I should do? Is
there maybe any workarounds?
>
> Thank you very much in advance for your response.
>
> Best regards,
> Mabi

________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users at gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users