-
Notifications
You must be signed in to change notification settings - Fork 155
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
[leo_storage][auto-compaction] Each storage node's data-compaction happened at almost same time #365
Comments
I've fixed this issue that each storage's data-compaction is executed step by step.
I've been considering calculation of |
I've reached the most suitable rule is as below:
I've considered that an auto-compaction processing needs to not affect front-end operations as much as possible.
|
According to a benchmark report, I/we have recognized we need to more improve the auto-compaction mechanism. I've been considering I implement a negotiation(consensus) mechanism w/candidate nodes of execution of a data-compaction. |
We've finally taken a good result - https://github.com/leo-project/notes/blob/master/leofs/benchmark/leofs/recover_with_front/20150629_recover_node_1.2.11-dev11/README.md |
@yosukehara |
@mocchira I've recognized that. But leo_storage was little bit old develop version. The latest version is works fine. Tomorrow, I'm planning to take a benchmark before LeoFS v1.2.11 release. |
Today, we've taken a benchmark - recover-node + front-operations w/watchdog and auto-compaction, which is good result for us. |
I've recognized an issue by a benchmark of LeoFS. The data-compaction of Leo's storage does not affect the front processing.
The text was updated successfully, but these errors were encountered: