Bug 1230095

Summary:	[geo-rep]: [doc]: if remove brick is performed using force to reduce the replica type. gsyncd wont kill for the removed bricks
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Rahul Hinduja <rhinduja>
Component:	geo-replication	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.1	CC:	avishwan, chrisw, csaba, nlevinki, sankarshan, sarumuga
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-16 15:55:57 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:	1223636

Description Rahul Hinduja 2015-06-10 08:51:53 UTC

Description of problem:
=======================

We make it mandate to stop the geo-rep session before performing remove-brick commit with the successful migration of data with start. But in a case we remove the brick from each subvolume, in other words if we decrease the replica count from 3 to 2 for example, both remove-brick start and commit will fail with usage to use "force". 

By using remove-brick force we bypass the validation of geo-rep and remove the bricks instantly which is expected with force, but this wont kill the gsyncd for all the removed-bricks.

Hence, a note section in document is needed to cover this corner case. 


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

glusterfs-3.7.1-1.el6rhs.x86_64