Bug 1468962

Summary:	[RFE] Have a global option to set per node limit to the number of multiplexed brick processes
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Atin Mukherjee <amukherj>
Component:	doc-Administration_Guide	Assignee:	Laura Bailey <lbailey>
doc-Administration_Guide sub component:	Default	QA Contact:	Prasanth <pprakash>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	asriram, nlevinki, puebele, rcyriac, rhs-bugs, rtalur, sasundar, shberry, storage-doc, storage-qa-internal
Version:	rhgs-3.3	Keywords:	FutureFeature, ZStream
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1468950	Environment:
Last Closed:	2021-05-04 00:19:36 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:

Comment 14 SATHEESARAN 2021-04-29 09:39:09 UTC

As I understand, with the current form of OCS 3.11, this option - max-brick-per-process is implicitly used and 
there is no change is recommended to this value.

I would suggest not to document this option, which would confuse users and they may play with this option
ending up in some problem.

This information should be useful in with KCS article but not in documentation.

Any thoughts ?

Comment 15 Raghavendra Talur 2021-04-29 12:14:21 UTC

(In reply to SATHEESARAN from comment #14)
> As I understand, with the current form of OCS 3.11, this option -
> max-brick-per-process is implicitly used and 
> there is no change is recommended to this value.
> 
> I would suggest not to document this option, which would confuse users and
> they may play with this option
> ending up in some problem.
> 
> This information should be useful in with KCS article but not in
> documentation.
> 
> Any thoughts ?

Yes, (In reply to SATHEESARAN from comment #14)
> As I understand, with the current form of OCS 3.11, this option -
> max-brick-per-process is implicitly used and 
> there is no change is recommended to this value.
> 
> I would suggest not to document this option, which would confuse users and
> they may play with this option
> ending up in some problem.
> 
> This information should be useful in with KCS article but not in
> documentation.
> 
> Any thoughts ?

Yes, I think we also went with a default in glusterd( See https://bugzilla.redhat.com/show_bug.cgi?id=1653073) that is set to 250. OCS just uses the default value as-is and it has been working fine so far.

Please close this bug.

Comment 16 SATHEESARAN 2021-05-04 00:19:36 UTC

(In reply to Raghavendra Talur from comment #15)
> (In reply to SATHEESARAN from comment #14)
> > As I understand, with the current form of OCS 3.11, this option -
> > max-brick-per-process is implicitly used and 
> > there is no change is recommended to this value.
> > 
> > I would suggest not to document this option, which would confuse users and
> > they may play with this option
> > ending up in some problem.
> > 
> > This information should be useful in with KCS article but not in
> > documentation.
> > 
> > Any thoughts ?
> 
> Yes, (In reply to SATHEESARAN from comment #14)
> > As I understand, with the current form of OCS 3.11, this option -
> > max-brick-per-process is implicitly used and 
> > there is no change is recommended to this value.
> > 
> > I would suggest not to document this option, which would confuse users and
> > they may play with this option
> > ending up in some problem.
> > 
> > This information should be useful in with KCS article but not in
> > documentation.
> > 
> > Any thoughts ?
> 
> Yes, I think we also went with a default in glusterd( See
> https://bugzilla.redhat.com/show_bug.cgi?id=1653073) that is set to 250. OCS
> just uses the default value as-is and it has been working fine so far.
> 
> Please close this bug.

Thanks Raghavendra for your comment.
Changes are no longer required