Bug 855306

Summary: geo-replication with large number of small static files will have E2BIG errors in logs.
Product: [Community] GlusterFS Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Csaba Henk <csaba>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: aavati, bbandari, csaba, gluster-bugs, rhs-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Too many arguments passed to rsync under heavy load Consequence: Random gysncd crashes; on some scenarios this was seen to accumulate to a critical mass and render the setup in a non-syncing state. Fix: Pass file list to rsync on stdin, not as arguments. Result: Works fine.
Story Points: ---
Clone Of: 855303 Environment:
Last Closed: 2013-03-19 07:34:13 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: 855303, 859173    
Bug Blocks:    

Description Vijaykumar Koppad 2012-09-07 10:18:38 UTC
+++ This bug was initially created as a clone of Bug #855303 +++

Description of problem:
If the geo-replication started with large number of small static files (around 2000000 files) , you get errors saying E2BIG

Version-Release number of selected component (if applicable):RHS-2.0.z


How reproducible:Higher probabilty if you work with 


Steps to Reproduce:
1.create 2000000 files on the master.
2.Then start the geo-rep session between the master and slave. 
3.Then wait for the E2BIG errors to happen in log files. 
  
Actual results: You get E2BIG errors in geo-rep log files 


Expected results: shouldn't get such errors 


Additional info:

Comment 1 Csaba Henk 2013-03-19 07:34:13 UTC
Fixed by

http://review.gluster.org/3917