Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

Thanks Hubert, I will try to run the script initially for future reference. From: Hu Bert Sent: 07 February 2024 6:55 AM To: Anant Saraswat Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

Have you tried setting up gluster georep with a dedicated non-root user ? Best Regards,Strahil Nikolov On Tue, Feb 6, 2024 at 16:38, Anant Saraswat wrote: Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge:

Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

That's not true for EL-based systems as they have 'glusterfsd.service' which on shutdown kills all gluster brick processes. Best Regards,Strahil Nikolov On Tue, Feb 6, 2024 at 9:21, Diego Zuccato wrote: Just a notice: bricks processes not being terminated prevents a simple "reboot" (or

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

No, It was setup and running using the root user only. Do you think I should setup using a dedicated non-root user? will it keep the track of old files or will it consider it as a new geo-replication and copy all the files from the scratch? From: Strahil

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

It will keep track of last sync time if you change to non-root user. But I don't think the issue is related to root vs non-root user.  Even in non-root user based Geo-rep, Primary volume is mounted using root user only. Only in the secondary node, it will use Glusterd mountbroker to allow

Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

If I might chip in here, this can cause an issue when rebooting nodes unless you make sure to stop the Gluster processes first. If you don't stop the processes, then the Gluster volumes can pause for the default 42 seconds(?) until the other nodes time out the rebooting node. This is of course

Re: [Gluster-users] __Geo-replication status is getting Faulty after few    seconds

Hi @Aravinda, I have checked the rsync version, and it's the same on primary and secondary nodes. We have rsync version 3.1.3, protocol version 31, on all servers. It's very strange that we have not made any changes, that we are aware of, and this geo-replication