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

Track level size by current version, or all versions? [JIRA: RIAK-2496] #191

Open
matthewvon opened this issue Apr 12, 2016 · 0 comments
Open

Comments

@matthewvon
Copy link
Contributor

A leveldb snapshot (created independently or as part of a database iterator) locks a set files on the disk. The files are part of some Version object, but not necessarily the most current Version. Therefore the logical disk size of the current Version can be greatly exceeded by the actual size of all files locked via snapshots.

Recent compaction selection logic that better supports tiered storage only uses logical disk size of current Version. It is therefore possible for a snapshot(s) to hold enough data in the fast tier to cause the fast tier to overflow. Compaction selection logic could greatly help in this overflow scenario if it used total space used by all Versions. (Remember that some files may appear in more than one version.)

@Basho-JIRA Basho-JIRA changed the title Track level size by current version, or all versions? Track level size by current version, or all versions? [JIRA: RIAK-2496] Apr 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants