Bug 1661511

Summary:	Add a step to set cluster.max-bricks-per-process to 250
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	doc-Container_Native_Storage_with_OpenShift	Assignee:	Chandrakanth Pai <chpai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	amukherj, asriram, chpai, kramdoss, rhs-bugs, sankarshan, storage-doc
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Async
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-15 10:16:11 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:

Description RamaKasturi 2018-12-21 12:27:16 UTC

Describe the Issue : Add a step on how to set cluster.max-brick-process to 250.

Document URL : https://access.qa.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Restoring_label

Section Name & Number : 6.2. & Restoring original label values for /dev/log

Suggestions for Improvement : Add the following steps under section 6.2 point and before point no.6 i.e before deleting the gluster pod

Issue the following command on one of the gluster pods to set the maximum number of bricks (250) that can run on a single instance of glusterfsd process: 				
# gluster volume set all cluster.max-bricks-per-process 250

i. Issue the following command on one of the gluster pods to ensure that the option is set correctly:
			
# gluster volume get all cluster.max-bricks-per-process

The output should show the following: 	
cluster.max-bricks-per-process 250


Additional Info :

Comment 5 RamaKasturi 2018-12-21 14:46:23 UTC

Verified in the link provided in comment 3 and the changes looks good to me.

Execute the following command on any one of the gluster pods to set the maximum number of bricks (250) that can run on a single instance of glusterfsd process:
# gluster volume set all cluster.max-bricks-per-process 250
Execute the following command on any one of the gluster pods to ensure that the option is set correctly:
# gluster volume get all cluster.max-bricks-per-process
For example:
# gluster volume get all cluster.max-bricks-per-process
cluster.max-bricks-per-process 250

Moving the bug to verified state.