Hi Felix,
If the geo-rep status is always initializing to faulty, we will not see any
syncing of files.
We would need full logs to analyse the issue.
Regards,
Shwetha
On Mon, Jul 13, 2020 at 7:39 PM Felix Kölzow wrote:
> Dear Shwetha,
>
> Can you elaborate this? Where are the same files
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
Hi Felix,
Find my reply inline.
Regards,
Shwetha
On Thu, Jun 25, 2020 at 12:25 PM Felix Kölzow 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
>
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
Dear Shwetha,
yes, I deleted the previous session including the [reset-sync-time] option.
Actually, the geo-replication is in hybrid crawl and I executed the command
what we discussed yesterday. # setfattr
So far, the files are still present on the slave side.
You mentioned that
Hi Felix,
Have you deleted the session with reset-sync-time and recreated the session?
If yes, the crawling starts from beginning.
Which happens in this way:
It begins with hybrid crawl, as data is already in master before re
creating the geo-rep session. If geo-rep session is craeted before
Dear Shwetha,
sorry, one more question, since I try to collect some more information
which may helpful for other gluster-users.
Does the suggested command
# setfattr -n glusterfs.geo-rep.trigger-sync -v "1"
also work regardless of the current mode, i.e. history, hybrid or
changelog crawl?
Dear Shwetha,
thanks for your reply. I mounted the volume via fuse on the
gluster storage server and ran the command:
setfattr -n glusterfs.geo-rep.trigger-sync -v "1"
Before that, I mounted the volume with my default options:
mount -t glusterfs -o acl glusterStorageServer:/volName
Hi Felix,
File path is the path from mount point. Need not include any other options.
Regards,|
Shwetha
On Mon, Jun 22, 2020 at 3:15 PM Felix Kölzow wrote:
> Dear Shwetha,
>
> > One more alternative would be to triggering sync on indivisual files,
> > # setfattr -n
Dear Shwetha,
One more alternative would be to triggering sync on indivisual files,
# setfattr -n glusterfs.geo-rep.trigger-sync -v "1"
So, how to do it exactly and what is ? Is it a gluster mount
point with certain mount options
or is this the brick path? Furthermore, does it work for
Deleting geo-rep session with reset-sync-time, makes sure that sync
time(stime) is reset. Sync time is last time when the sync happened from
master to slave.
Regards,
Shwetha
On Mon, Jun 22, 2020 at 2:42 PM Shwetha Acharya wrote:
> Hi Felix,
>
> Index here is stime or sync time. Once we set
Hi Felix,
Index here is stime or sync time. Once we set sync time to 0, crawl happens
from the beginning, till stime < xtime. (xtime is last modified time of
file or directory on master)
We can achieve it using following steps:
# gluster volume geo-replication master-vol slave-ip::slave-vol stop
Dear Shwetha,
thank you very much for your immediate response.
It turns out we have rsync 3.1.2, so this sould be fine.
Actually, geo-rep is in xsync mode, but just due to
the fact that I deleted the geo-replication and used the reset-sync-time
option.
If you are looking to still resync,
Would it be possible for you to provide more specifics about the
issues you see and the release in which these are seen?
Some files on the slave side still exist, while they are deleted on the
master side many month ago. Due to
another issue, I would like to initiate a re-sync just to assure
On Fri, 19 Jun 2020 at 18:16, Felix Kölzow wrote:
>
> Dear Gluster-Users,
>
>
> as I am seeing some issues with the geo-replication, I would like to
> collect some more
>
> user experience and workarounds if issues occur.
>
Would it be possible for you to provide more specifics about the
issues
Dear Gluster-Users,
as I am seeing some issues with the geo-replication, I would like to
collect some more
user experience and workarounds if issues occur.
Some workarounds are already documented, but that seems to be not
detailed enough.
So I would like to know how reliable is your
16 matches
Mail list logo
