Bug 951469

Summary:	Gluster_File_System Administration_Guide-en-US.pdf cluster.quorum-type, log-level
Product:	[Community] Gluster-Documentation	Reporter:	Nagilum <bugzilla>
Component:	Other	Assignee:	Anjana Suparna Sriram <asriram>
Status:	NEW ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
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:	---	Target Upstream Version:
Embargoed:

Description Nagilum 2013-04-12 09:45:03 UTC

Description of problem:
The Administration guide does not list "cluster.quorum-type" in the options table.

The guide lists these as possible values for *-log-level:
DEBUG|WARNING|
ERROR|CRITICAL|
NONE|TRACE

Yet at the same time it lists 'INFO' as the default which is not a possible value according to the column next to it.

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

How reproducible:
Compare http://www.gluster.org/wp-content/uploads/2012/05/Gluster_File_System-3.3.0-Administration_Guide-en-US.pdf and http://gluster.org/community/documentation/index.php/Gluster_3.2:_Setting_Volume_Options#cluster.quorum-type

Additional info:
From the wiki:
cluster.quorum-type 	Method used for quorum enforcement. "None" means no quorum enforcement, which is the historical behavior. "Auto" means quorum is set to be more than half of the bricks in a subvolume, or exactly half if that includes the first listed brick. "Fixed" means quorum is set to a value specified by cluster.quorum-count. If quorum is not met, then modifing operations such as write will fail with EROFS. This prevents most cases of "split brain" which result from conflicting writes to different bricks. 	

Default: None