Bug 1461027

Summary:	[RFE] Provide an option not to kill the bricks, when server-quorum is not met
Product:	[Community] GlusterFS	Reporter:	SATHEESARAN <sasundar>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, pkarampu, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 05:19:40 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:	1461028

Description SATHEESARAN 2017-06-13 12:03:21 UTC

Description of problem:
-----------------------
server-quorum when not met kills the brick process on that node. This affects the data path.

It would be useful to provide the flexibility to choose the behavior of **not** killing the bricks under the circumstance of server-quorum not met scenario.

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

How reproducible:
-----------------
Not Applicable for feature enhancement

Steps to Reproduce:
-------------------
Not applicable for feature enhancement

Actual results:
---------------
Bricks are killed when server-quorum not met

Expected results:
-----------------
Provide the flexibility to opt for **not** killing the bricks, when server-quorum  is not met

Additional info:
----------------
The motivation for this bug resulted from the gluster user who has complained about data-path that is affected as result of loss of 2 nodes in a 4 node cluster. In this case, all the virtual machines running on the gluster volume got paused.

Comment 1 Vijay Bellur 2018-11-19 05:25:50 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/582

Please follow the github issue for further updates on this bug.