Re: Reliable Geo-Replication

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Shwetha,

Can you elaborate this? Where are the same files appearing? Are they getting synced
I changed to geo-repl config log_level to DEBUG and observed the log-file.

Already the same files are going to be synced again and again. Furthermore,

some files were marked as synced candidate but nothing happens.

There is no network traffic, the disk are almost idle and just nothing happens.

No progress can be observed, even after 3 weeks of this state.


Currently, it changes from from faulty to initializing to fauly and so forth. No worker is currently

active or passive.


Regards,

Felix

On 09/07/2020 13:29, Shwetha Acharya wrote:
Hi Felix,

Find my reply inline.

Regards,
Shwetha

On Thu, Jun 25, 2020 at 12:25 PM Felix Kölzow <felix.koelzow@xxxxxx> wrote:
Dear Gluster-users,

I deleted a further the geo-replication session with [reset-sync-time]
option. Afterwards,
I recreated the session, and as expected, the session starts in the
hybrid crawl.
I can see some sync jobs are running in the gsyncd.log file and after a
couple of hours,
there are no such entries anymore.

I switched into the log_level DEBUG mode to see what's going on:
gluster volume masterVOlume geoRepHost:slaveVol config log_level DEBUG

It seems to me that the xsync mode is in loop since the same files
appear over and over again in the log-file.
Can you elaborate this? Where are the same files appearing? Are they getting synced 

Now we have two volume in this "loop"-state and the third volume also
still has a broken geo-replication.

Is the worker status changing from initializing to faulty or initializing to active/passive? Is any worker active?  
So any help is appreciated how to fix this or which information is
required to find the root cause?

As mentioned before, all these gathered information could be used to
improve the geo-replication trouble-shooting documentation.

Thanks in advance.

Regards,
Felix
________



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


________



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



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

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux