Bug 969384 - [FEAT] Reduce the number of crawls the self-heal daemon needs to make
Summary: [FEAT] Reduce the number of crawls the self-heal daemon needs to make
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Krutika Dhananjay
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 917686
TreeView+ depends on / blocked
 
Reported: 2013-05-31 10:34 UTC by Niels de Vos
Modified: 2015-10-22 15:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:46:38 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Niels de Vos 2013-05-31 10:34:13 UTC
It seems that the self-heal daemon needs N+1 crawls of the volume (where N is
the maximum depth of the directory structure). At the moment, the indexes that
are used by the self-heal daemon do not have any ordering information. If
there would be some ordering, it would be possible to heal directories first,
and files afterwards. The number of crawls could be reduced that way and the
errors related to healing files in directories that do not exist yet would be
prevented (see Bug 969353).

Comment 1 Pranith Kumar K 2014-04-22 04:43:14 UTC
We found one way to do this where the number of crawls could be reduced to 2 irrespective of the depth of directory structure. I recently discovered that posix has the ability to give full directory hierarchy given any directory gfid because .glusterfs of the brick stores a softlink for <pargfid>/dirname for every directory. So in the first crawl for every directory self-heal-daemon needs to heal the entire directory hierarchy (i.e create/delete the files). Then only files will remain to be healed which will be healed in the second crawl i.e. metadata/data heals.

Pranith

Comment 2 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.


Note You need to log in before you can comment on or make changes to this bug.