Bug 1729483 - Thin-arbiter: SHD takes lock and inspects the state on TA during every index crawl
Summary: Thin-arbiter: SHD takes lock and inspects the state on TA during every index ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: 7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karthik U S
QA Contact:
URL:
Whiteboard:
Depends On: 1724184
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-12 11:49 UTC by Karthik U S
Modified: 2019-07-24 11:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1724184
Environment:
Last Closed: 2019-07-24 11:02:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23037 0 None Merged cluster/ta: Notify the clients only if there are pending heals 2019-07-24 11:02:24 UTC

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
Note You need to log in before you can comment on or make changes to this bug.