Bug 1025951 - slave's timestamp mark attr should be '*.stime'
Summary: slave's timestamp mark attr should be '*.stime'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1036539
Blocks: 1025953
TreeView+ depends on / blocked
 
Reported: 2013-11-02 13:13 UTC by Venky Shankar
Modified: 2014-12-29 04:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1025953 (view as bug list)
Environment:
Last Closed: 2014-12-29 04:52:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Venky Shankar 2013-11-02 13:13:05 UTC 
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 14:41:23 UTC 
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)
Comment 2 Aravinda VK 2014-12-29 04:52:33 UTC 
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.