Bug 1026072

Summary:	Dist-geo-rep : After node reboot, all the changelog files in .processed dir of geo-rep working directory will be deleted
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	geo-replication	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED DUPLICATE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	aavati, asriram, avishwan, csaba, david.macdonald, psriniva, rwheeler, vshankar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-24 09:13:10 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:
Bug Blocks:	1020127

Description Vijaykumar Koppad 2013-11-03 11:46:06 UTC

Description of problem:After node reboot, all the files in .processed dir of geo-rep  working directory will be cleared.  


Version-Release number of selected component (if applicable):
glusterfs-3.4.0.38rhs

How reproducible:Happens everytime. 


Steps to Reproduce:
1.Create and start a geo-rep relationship between master(dist-rep) and slave
2.create some data on master and let it sync to slave. 
3.Bring down a node ( active or passive) 
4.create some data on master and let it sync. 
5.bring back the node. 
4.check the files in .processed dir of geo-rep working dir. 

Actual results: It deletes  all the changelog files from .processed dir.


Expected results: It shouldn't delete any of the changelog files form processed. 


Additional info:

Comment 2 Venky Shankar 2013-11-14 10:53:22 UTC

possibly /var being temporary?

Amar, any alternative for $working_dir in geo-replication?

Comment 3 Pavithra 2013-11-25 08:49:13 UTC

After a discussion with Amar, this bug was decided to be documented as a known issue in the Big Bend Update 1 Release Notes. Here is the link:

http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Storage/2.1/html/2.1_Update_1_Release_Notes/chap-Documentation-2.1_Update_1_Release_Notes-Known_Issues.html

Comment 5 Aravinda VK 2014-12-24 09:13:10 UTC


*** This bug has been marked as a duplicate of bug 1095314 ***