Bug 1724184

Summary:	Thin-arbiter: SHD takes lock and inspects the state on TA during every index crawl
Product:	[Community] GlusterFS	Reporter:	Karthik U S <ksubrahm>
Component:	replicate	Assignee:	Karthik U S <ksubrahm>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1729483 (view as bug list)		Environment:
Last Closed:	2019-07-12 11:19:15 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:	1729483

Description Karthik U S 2019-06-26 12:26:53 UTC

Description of problem:

For thin arbiter volumes, even if there are no entries needing heal, SHD will take a lock on TA in AFR_TA_DOM_NOTIFY domain and gets the state and then unlocks. This will lead to invalidation of cached information on clients about the bricks state even though there is no pending heal. This happens during index crawl at every heal-timeout interval.

SHD should not take the lock on TA and invalidate the cached data on clients if there is no pending heal.

Comment 1 Worker Ant 2019-06-26 12:41:42 UTC

REVIEW: https://review.gluster.org/22950 (cluster/ta: Notify the clients only if there are pending heals) posted (#1) for review on master by Karthik U S

Comment 2 Worker Ant 2019-07-12 11:19:15 UTC

REVIEW: https://review.gluster.org/22950 (cluster/ta: Notify the clients only if there are pending heals) merged (#7) on master by Ravishankar N