Slave's time in log is not reporting Slave cluster's current time. It is
logging the time till Slave cluster is in sync with respect to current
Master node.
From the log information below,
Master node's time is 2017-11-22 00:59:40.610574
Files/dirs synced to Slave cluster from the current node till
(1511312352, 0) ie, Tuesday, November 21, 2017 12:59:12 AM GMT
Geo-rep yet to sync the difference from current node to Slave cluster
(2017-11-22 00:59:40.610574 - Tuesday, November 21, 2017 12:59:12 AM GMT)
Sorry for the wrong message from the log files. I will work on it to
change the log message into meaningful.
--
regards
Aravinda VK
http://aravindavk.in
On Saturday 25 November 2017 07:48 AM, Mark Connor wrote:
Folks, need help interpreting this message from my geo rep logs for my
volume mojo.
ssh%3A%2F%2Froot%40173.173.241.2%3Agluster%3A%2F%2F127.0.0.1%3Amojo-remote.log:[2017-11-22
00:59:40.610574] I [master(/bricks/lsi/mojo):1125:crawl] _GMaster:
slave's time: (1511312352, 0)
The epoch of 1511312352 is Tuesday, November 21, 2017 12:59:12 AM GMT.
The clocks are using the same ntp stratum and seem right on the money
for master and slave.
Why the difference in seconds after taking into account the timezones?
Anyone know where both timestamps come from?
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
