<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed May 22 10:29:22 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/si/jira.issueviews:issue-xml/MB-6976/MB-6976.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[MB-6976] Make checkpoint_flush_timeout adjustable at runtime</title>
                <link>http://www.couchbase.com/issues/browse/MB-6976</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>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.</description>
                <environment></environment>
            <key id="20341">MB-6976</key>
            <summary>Make checkpoint_flush_timeout adjustable at runtime</summary>
                <type id="4" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="chiyoung">Chiyoung Seo</assignee>
                                <reporter username="chiyoung">Chiyoung Seo</reporter>
                        <labels>
                    </labels>
                <created>Fri, 19 Oct 2012 21:15:09 -0500</created>
                <updated>Mon, 12 Nov 2012 16:27:52 -0600</updated>
                    <resolved>Mon, 22 Oct 2012 17:47:23 -0500</resolved>
                            <version>2.0-beta</version>
                                <fixVersion>2.0</fixVersion>
                                <component>couchbase-bucket</component>
                <component>cross-datacenter-replication</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="42218" author="chiyoung" created="Mon, 22 Oct 2012 17:47:23 -0500"  >&lt;a href=&quot;http://review.couchbase.org/#/c/21857/&quot;&gt;http://review.couchbase.org/#/c/21857/&lt;/a&gt;</comment>
                    <comment id="42360" author="thuan" created="Tue, 23 Oct 2012 20:24:32 -0500"  >Integrated in github-ep-engine-2-0 #447 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ep-engine-2-0/447/&quot;&gt;http://qa.hq.northscale.net/job/github-ep-engine-2-0/447/&lt;/a&gt;])&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-6976&quot; title=&quot;Make checkpoint_flush_timeout adjustable at runtime&quot;&gt;&lt;strike&gt;MB-6976&lt;/strike&gt;&lt;/a&gt; Make checkpoint_flush_timeout adjustable at runtime (Revision 6640037b5ca06ea5dde0295dc65b254661719e4a)&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Result = SUCCESS&lt;br/&gt;
Chiyoung Seo : &lt;br/&gt;
Files : &lt;br/&gt;
* docs/stats.org&lt;br/&gt;
* src/ep.cc&lt;br/&gt;
* src/flusher.hh&lt;br/&gt;
* tests/ep_testsuite.cc&lt;br/&gt;
* src/flusher.cc&lt;br/&gt;
* src/ep_engine.cc&lt;br/&gt;
</comment>
                    <comment id="43843" author="kzeller" created="Mon, 12 Nov 2012 16:27:52 -0600"  >Added to RN: The default timeout for persisting a checkpoint had been 10 seconds. This default &lt;br/&gt;
is still in place, but will now be adjusted upward or downward by the server to &lt;br/&gt;
be the last duration required to persist a checkpoint. This is to better &lt;br/&gt;
optimize server resources for indexing during rebalance.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Tue, 23 Oct 2012 20:24:32 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                        <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>3694</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                                                                    <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>