On 16/07/2019 15:27, Ravishankar N wrote:
Yes, if you simply pkill the gluster brick processes of the node before
switching it off, you won't observe the hang on the clients because they
will receive the disconnect notification immediately. But before that,
you would need to check if there are
On Tue, 2019-07-16 at 13:24 +0530, deepu srinivasan wrote:
> Hi Users
> Is there a way to know the stats of geo-replication like the transfer
> rate, amount of data and number of the file transferred in Geo-
> Replication?
Last synced time column in status output represents the time till data
is
Rebalance is not dependent on Geo-replication. New workers will start
with Hybrid crawl and syncs the files created by Rebalance. Rebalance
on slave side will not affect Geo-replication since it syncs through
mount.
On Tue, 2019-07-16 at 16:26 +0530, deepu srinivasan wrote:
> Thanks a lot,
Hi list,
I have a replica 3 test cluster and I have a question about how clients
behave to an host shutdown.
If I suddenly switch off one of the gluster server, the connected
clients see a ~42s stall in I/O: this is expected, as it is the default
client timeout.
However, it is possible to
There were some issues with gluster v3.12.x to v5.x, but we haven't heard
any major problems with v3.12.x to v6.x version, other than
https://bugzilla.redhat.com/show_bug.cgi?id=1727682 which also seems to be
all resolved now.
Regards,
Amar
On Thu, Jul 11, 2019 at 11:16 PM Strahil wrote:
>
On Thu, Jul 11, 2019 at 11:15 PM Strahil wrote:
> I'm addding gluster-users as I'm not sure if you can go gluster v3 -> v6
> directly.
>
> Theoretically speaking , there should be no problem - but I don't know
> if you will observe any issues.
>
> @Gluster-users,
>
> Can someone share their
