New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct the metadata GC behavior if PathIndexing is not up to date #7

Closed
hdsdi3g opened this Issue Mar 4, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@hdsdi3g
Owner

hdsdi3g commented Mar 4, 2014

If storage has troubles for a while -> error during pathindexing, so no update last task executed, and hence no analysis of metadatas.
Then TTL will delete all Storage content, and metadata GC will purge all metadatas...
Purging metadatas should not purge these elements and thus make a check for the last executed task..

@hdsdi3g hdsdi3g added this to the Beta version milestone Mar 4, 2014

@hdsdi3g hdsdi3g added bug labels Mar 4, 2014

@hdsdi3g hdsdi3g self-assigned this Mar 4, 2014

@hdsdi3g hdsdi3g added the dvl-mtdfile label Mar 9, 2014

@hdsdi3g hdsdi3g removed their assignment Mar 15, 2014

hdsdi3g added a commit that referenced this issue Apr 4, 2014

@hdsdi3g

This comment has been minimized.

Show comment
Hide comment
@hdsdi3g

hdsdi3g Apr 4, 2014

Owner

Simply search if pathindexing is empty for a storage (cache results during a gc session).

Owner

hdsdi3g commented Apr 4, 2014

Simply search if pathindexing is empty for a storage (cache results during a gc session).

@hdsdi3g hdsdi3g closed this Apr 4, 2014

@hdsdi3g hdsdi3g self-assigned this Jun 26, 2014

@hdsdi3g hdsdi3g reopened this Dec 15, 2016

hdsdi3g added a commit that referenced this issue Dec 15, 2016

@hdsdi3g hdsdi3g closed this Dec 15, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment