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

Poor GC of leveled during handoff #1699

Closed
martinsumner opened this issue May 23, 2019 · 2 comments
Closed

Poor GC of leveled during handoff #1699

martinsumner opened this issue May 23, 2019 · 2 comments
Labels
2.9 Known Issue Known issues with the Riak 2.9 release

Comments

@martinsumner
Copy link
Contributor

During handoff (i.e. a node transfer), the PUT rate into a vnode may be higher than normal.

During the 2.9 cycle of release candidates, a change was introduced to do per-process GC on leveled_sst files if they still exist 10s after they were created. This stopped an issue with poor GC on these processes when running Riak on OTP16.

When put pressure is high, level 1 files may be moved to the delete_pending state (because they have been replaced), before the GC message is received. The GC message broke the timeout loop on delete, meaning that the file process would not correctly self-delete until the vnode is shutdown. This could lead to issues with the ulimit open files limit.

@martinsumner martinsumner added the 2.9 Known Issue Known issues with the Riak 2.9 release label May 23, 2019
@martinsumner
Copy link
Contributor Author

This could also have an impact where leveled is used as a Tictac AAE backend.

martinsumner added a commit to martinsumner/riak_kv that referenced this issue May 23, 2019
To include fixes for basho#1699
@martinsumner
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.9 Known Issue Known issues with the Riak 2.9 release
Projects
None yet
Development

No branches or pull requests

1 participant