Bug 1723680

Summary:	RHV Reduce polling interval for gluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rhhiv-1.6	CC:	abhishku, godas, guillaume.pavese, kmajumde, lsurette, mtessun, rhs-bugs, sabose, seamurph, srevivo, ycui
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHHI-V 1.6.z Async Update
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1530495	Environment:
Last Closed:	2019-09-06 05:23:04 UTC	Type:	---
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:	1530495
Bug Blocks:

Comment 1 SATHEESARAN 2019-06-25 07:06:42 UTC

Description of problem:

To fix the locking issue, RHV monitoring of gluster will need to change to use get-state and aggregate information collected from each node

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

NA


Additional info:

Currently, Vdsm triggering many call per status check which is resulting in failed locking inside gluster. This is stopping user to run any manual gluster related commands, since locks are already held.

Comment 2 SATHEESARAN 2019-07-26 15:18:27 UTC

Tested with RHV 4.3.3

'gluster volume status detail' is queried for every 15 mins

[2019-07-26 15:00:38.425519]  : system:: uuid get : SUCCESS
[2019-07-26 15:00:54.035630]  : system:: uuid get : SUCCESS
[2019-07-26 15:01:09.674883]  : system:: uuid get : SUCCESS
[2019-07-26 15:01:12.398454]  : volume status vmstore : SUCCESS
[2019-07-26 15:01:12.586130]  : volume status vmstore detail : SUCCESS
[2019-07-26 15:01:16.200499]  : volume status engine : SUCCESS
[2019-07-26 15:01:16.378735]  : volume status engine detail : SUCCESS
[2019-07-26 15:01:19.968367]  : volume status non_vdo : SUCCESS
[2019-07-26 15:01:20.152647]  : volume status non_vdo detail : SUCCESS
[2019-07-26 15:01:23.795427]  : volume status data : SUCCESS
[2019-07-26 15:01:23.984186]  : volume status data detail : SUCCESS
<lines-snipped>
[2019-07-26 15:16:27.651132]  : volume status vmstore : SUCCESS
[2019-07-26 15:16:27.835725]  : volume status vmstore detail : SUCCESS
[2019-07-26 15:16:31.528667]  : volume status engine : SUCCESS
[2019-07-26 15:16:31.708591]  : volume status engine detail : SUCCESS
[2019-07-26 15:16:35.358410]  : volume status non_vdo : SUCCESS
[2019-07-26 15:16:35.538591]  : volume status non_vdo detail : SUCCESS
[2019-07-26 15:16:36.997835]  : system:: uuid get : SUCCESS
[2019-07-26 15:16:39.815920]  : volume status data : SUCCESS
[2019-07-26 15:16:40.006440]  : volume status data detail : SUCCESS