Bug 1025951 - slave's timestamp mark attr should be '*.stime'
slave's timestamp mark attr should be '*.stime'
Status: CLOSED CURRENTRELEASE
Product: GlusterFS
Classification: Community
Component: geo-replication (Show other bugs)
mainline
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: bugs@gluster.org
:
Depends On: 1036539
Blocks: 1025953
  Show dependency treegraph
 
Reported: 2013-11-02 09:13 EDT by Venky Shankar
Modified: 2014-12-28 23:52 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1025953 (view as bug list)
Environment:
Last Closed: 2014-12-28 23:52:33 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Venky Shankar 2013-11-02 09:13:05 EDT
Description of problem:
Currently, slave's timestamp marker is "*.xtime", but for correct processing and pruning of changelogs from the passive node, 'stime' key helps in identifying how much the slave is lagging. For this, the slave's timestamp marker key needs to be "*.stime" instead of "*.xtime" as 'stime' has special processing (min/max) in GlusterFS that correctly identifies the lag.

Version-Release number of selected component (if applicable):
mainline
Comment 1 Anand Avati 2013-11-02 10:41:23 EDT
REVIEW: http://review.gluster.org/6216 (gsyncd / geo-rep: slave's xtime key is 'stime') posted (#1) for review on master by Venky Shankar (vshankar@redhat.com)
Comment 2 Aravinda VK 2014-12-28 23:52:33 EST
The patch http://review.gluster.org/#/c/6404/ fixes this bug as part of bz 1036539

Note You need to log in before you can comment on or make changes to this bug.