Bug 1636872

Summary:	allow creating or deleting volumes back to back without the need of delay (ie get rid of sleep of 2 sec)
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED NOTABUG	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	jmulligan, nchilaka, rhs-bugs, sankarshan, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
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:	2018-10-12 05:49:04 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:	1637787

Description Nag Pavan Chilakam 2018-10-08 07:36:16 UTC

Description of problem:
-------------------
if we have multiple volumes which we want to create/delete or if we want to create multiple vols, back to back, we need to put a sleep of 2 seconds, so as to avoid stale brick processes related issues.
However, we need to fix this so that we dont have to put a sleep of 2 seconds, given that, this is not a feasible approach for OCS, in my belief.

Also, on another node, I am not sure if heketi/OCS provision takes care of inducing sleep of 2 sec.


Version-Release number of selected component (if applicable):
=======================
3.12.2-21

expected behavior:
===============
enhance gluster to take in parallel requests for vol create/del without the need of delays induced(internally gluster can queue them if need be)


refer admin docs for checking if we are asking customers to induce delay
eg: 
https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/administration_guide/

23.3.2. Enabling Management Encryption

Comment 2 Atin Mukherjee 2018-10-08 11:39:25 UTC

"if we have multiple volumes which we want to create/delete or if we want to create multiple vols, back to back, we need to put a sleep of 2 seconds, so as to avoid stale brick processes related issues."

- What's the justification on the stale brick process here? What am I missing? Mind to point to a BZ?

Comment 3 Atin Mukherjee 2018-10-08 11:40:03 UTC

Also why the Internal Whiteboard has been marked as 3.4.1? Are you proposing this as blocker to 3.4.1? Again, what's the justification?

Comment 4 John Mulligan 2018-10-08 18:23:53 UTC

> Also, on another node, I am not sure if heketi/OCS provision takes care of inducing sleep of 2 sec.

No, to the best of my knowledge Heketi does not enforce a delay or sleep of 2 seconds between volume deletes. 

This is also the first I've heard of this recommendation. I couldn't find it in the docs you linked to, but I'm not sure if you were saying that it should be added to the docs or was noted in the docs. If the latter, an excerpt from the docs might be useful.

Comment 5 Atin Mukherjee 2018-10-09 04:28:56 UTC

Needinfo should remain to the reporter as I haven't seen the response yet on my questions :-)

Comment 6 Atin Mukherjee 2018-10-10 04:31:24 UTC

Nag - I have an open question at this bug at comment 2. Please answer to it, otherwise this bug will be closed with a resolution as insufficient data.