Disable merges on startup to prevent high disk io with heavy requests
Closed this issue · 2 comments
Sometimes, bitcask will merge on node startup. This can cause very high disk IO when paired with lots of requests and can result in request timeouts and very high FSM times. Adding a timer on startup for bitcask merges may reduce this occurrence. Another idea is to disable bitcask merging during full-syncs or high volume of client requests.
merge check is initially scheduled for three minutes from startup. do you mind if I close this in favor of #117? could you add a comment there specifying the initial period you'd like to see?
Close it. I think that issue is a better place for this idea. Goal would be
to wait until after kv has finished starting.
On Nov 7, 2013 2:44 PM, "Evan Vigil-McClanahan" notifications@github.com
wrote:
merge check is initially scheduled for three minutes from startup. do you
mind if I close this in favor of #117#117?
could you add a comment there specifying the initial period you'd like to
see?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-27999382
.