Bug 1025951

Summary:	slave's timestamp mark attr should be '*.stime'
Product:	[Community] GlusterFS	Reporter:	Venky Shankar <vshankar>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	avishwan, bugs, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1025953 (view as bug list)		Environment:
Last Closed:	2014-12-29 04:52:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1036539
Bug Blocks:	1025953

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