Bug 1461027 - [RFE] Provide an option not to kill the bricks, when server-quorum is not met
[RFE] Provide an option not to kill the bricks, when server-quorum is not met
Status: NEW
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
mainline
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: bugs@gluster.org
: FutureFeature, Triaged
Depends On:
Blocks: 1461028
  Show dependency treegraph
 
Reported: 2017-06-13 08:03 EDT by SATHEESARAN
Modified: 2017-07-02 23:43 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description SATHEESARAN 2017-06-13 08:03:21 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.