Skip to content
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

trim: gc and client barrier for reclaim #371

Open
dotnwat opened this issue Jul 17, 2019 · 0 comments
Open

trim: gc and client barrier for reclaim #371

dotnwat opened this issue Jul 17, 2019 · 0 comments

Comments

@dotnwat
Copy link
Member

dotnwat commented Jul 17, 2019

there is an issue with trim where we leave behind old objects as placeholders. just the object and the header, but no content. these can be cleaned up after some sufficiently long period that clients don't hold state referring to them. however... we could use something like rados watch/notify to add a barrier that updates inflight clients to allow objects to be reclaimed. if we do this, we should be sure to use a backend interface that doesn't depend on watch/notify-type implementation details specifically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant