[MB-6976] Make checkpoint_flush_timeout adjustable at runtime Created: 19/Oct/12 Updated: 12/Nov/12 Resolved: 22/Oct/12
|Reporter:||Chiyoung Seo||Assignee:||Chiyoung Seo|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
VBucket flush prioritization has the timeout on vbucket checkpoint persistence. The timeout needs to be adjusted at runtime in order to give more flexibilities to the external components that requests the prioritization.
|Comment by Chiyoung Seo [ 22/Oct/12 ]|
|Comment by Thuan Nguyen [ 23/Oct/12 ]|
Integrated in github-ep-engine-2-0 #447 (See [http://qa.hq.northscale.net/job/github-ep-engine-2-0/447/])|
Result = SUCCESS
Chiyoung Seo :
|Comment by kzeller [ 12/Nov/12 ]|
Added to RN: The default timeout for persisting a checkpoint had been 10 seconds. This default
is still in place, but will now be adjusted upward or downward by the server to
be the last duration required to persist a checkpoint. This is to better
optimize server resources for indexing during rebalance.