Bug 1171313

Summary: Failure to sync files to slave with 2 bricks.
Product: [Community] GlusterFS Reporter: vnosov <vnosov>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: medium    
Version: 3.6.1CC: avishwan, bugs, vnosov
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-19 11:43:59 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:
Attachments:
Description Flags
Gluster logs from master and slave systems. none

Description vnosov 2014-12-05 21:30:55 UTC
Created attachment 965232 [details]
Gluster logs from master and slave systems.

Description of problem:

Geo-replication does not sync files and directories from master to slave volume if slave volume is distributed volume with more than 1 brick. Geo-replication to slave volume with single brick is maintaining synchronization properly.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
see attached logs.

Comment 1 vnosov 2015-04-20 23:00:29 UTC
Was not able duplicate this bug with version 3.6.2.

Comment 2 Aravinda VK 2016-08-19 11:43:59 UTC
This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.