[MB-6976] Make checkpoint_flush_timeout adjustable at runtime Created: 19/Oct/12  Updated: 12/Nov/12  Resolved: 22/Oct/12

Status: Resolved
Project: Couchbase Server
Component/s: couchbase-bucket, cross-datacenter-replication
Affects Version/s: 2.0-beta
Fix Version/s: 2.0
Security Level: Public

Type: Improvement Priority: Major
Reporter: Chiyoung Seo Assignee: Chiyoung Seo
Resolution: Fixed Votes: 0
Labels: None
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/])
    MB-6976 Make checkpoint_flush_timeout adjustable at runtime (Revision 6640037b5ca06ea5dde0295dc65b254661719e4a)

     Result = SUCCESS
Chiyoung Seo :
Files :
* docs/stats.org
* src/ep.cc
* src/flusher.hh
* tests/ep_testsuite.cc
* src/flusher.cc
* src/ep_engine.cc
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.
Generated at Tue Sep 23 15:04:06 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.