Bug 984942

Summary: Dist-geo-rep : rebalance start on master volume triggers geo-rep and consequently deletes few files from slave.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED ERRATA QA Contact: Vijaykumar Koppad <vkoppad>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1CC: aavati, amarts, bbandari, csaba, rhs-bugs, sdharane, shaines
Target Milestone: ---Keywords: TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.12rhs.beta6-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:29:51 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: 985236, 989532    

Description Vijaykumar Koppad 2013-07-16 12:34:09 UTC
Description of problem: Add-brick and rebalance start will trigger geo-rep syncing and which results in deleting and creating few files on the slave ( ie number of files on slave goes up and down), and the geo-rep keeps on logging  
 "failed to sync" logs in geo-rep log-file. It will also have constant number of files in .processing directory.  

Version-Release number of selected component (if applicable): 3.4.0.12rhs.beta4-1.el6rhs.x86_64


How reproducible: Haven't tried to reproduce it. 


Steps to Reproduce:
1. Create and start geo-rep relationship between master(DIST_REP) and slave. 
2. Now add-brick and start rebalance on master. 
3. Check the number of files on the slave and also check geo-rep logs.

Actual results: Rebalance start triggers geo-rep and deletes few files from slave. 


Expected results: Rebalance shouldn't trigger geo-rep. 


Additional info:

Comment 4 Vijaykumar Koppad 2013-07-24 08:51:45 UTC
Verified in glusterfs-3.4.0.12rhs.beta6-1,

Comment 5 Scott Haines 2013-09-23 22:29:51 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html