Bug 1729483

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:	7	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:	1724184	Environment:
Last Closed:	2019-07-24 11:02:25 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:	1724184
Bug Blocks:

Description Karthik U S 2019-07-12 11:49:53 UTC

+++ This bug was initially created as a clone of Bug #1724184 +++

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.

Comment 1 Worker Ant 2019-07-12 12:02:08 UTC

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

Comment 2 Worker Ant 2019-07-24 11:02:25 UTC

REVIEW: https://review.gluster.org/23037 (cluster/ta: Notify the clients only if there are pending heals) merged (#3) on release-7 by Rinku Kothiya