Re: [Gluster-users] Monitoring tools for GlusterFS

2020-08-23 Thread Sachidananda Urs 
On Sat, Aug 22, 2020 at 10:52 PM Artem Russakovskii 
wrote:

> The output currently has some whitespace issues.
>
> 1. The space shift under Cluster is different than under Volumes, making
> the output look a bit inconsistent.
> 2. Can you please fix the tabulation for when volume names are varying in
> length? This output is shifted and looks messy as a result for me.
>

Artem, since the volume names vary for longer volumes the column number
increases and users have to scroll to right.
To overcome this, I have decided to print the volume name in a row by
itself.  PR: https://github.com/gluster/gstatus/pull/44 fixes the issue.

The output looks like this:

root@master-node:/home/sac/work/gstatus# gstatus


Cluster:

 Status: Healthy GlusterFS: 9dev

 Nodes: 3/3  Volumes: 2/2


Volumes:


snap-1

Replicate  Started (UP) - 2/2 Bricks Up

   Capacity: (12.04% used) 5.00 GiB/40.00
GiB (used/total)

   Snapshots: 2

   Quota: On


very_very_long_long_name_to_test_the_gstatus_display

Replicate  Started (UP) - 2/2 Bricks Up

   Capacity: (12.04% used) 5.00 GiB/40.00
GiB (used/total)



root@master-node:/home/sac/work/gstatus#


-sac




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@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade from 6.9 to 7.7 stuck (peer is rejected)

2020-08-23 Thread 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  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@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users