<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 08:44:02 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-4418/MB-4418.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-4418] Allow disk write queue cap to be modified at runtime</title>
                <link>http://www.couchbase.com/issues/browse/MB-4418</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description></description>
                <environment></environment>
            <key id="15555">MB-4418</key>
            <summary>Allow disk write queue cap to be modified 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="mikew">Mike Wiederhold</assignee>
                                <reporter username="perry">Perry Krug</reporter>
                        <labels>
                        <label>1.8.0-release-notes</label>
                        <label>1.8.1-release-notes</label>
                    </labels>
                <created>Thu, 10 Nov 2011 22:42:21 -0600</created>
                <updated>Wed, 16 May 2012 18:16:19 -0500</updated>
                    <resolved>Thu, 10 May 2012 18:31:08 -0500</resolved>
                            <version>1.8.0</version>
                                <fixVersion>1.8.1</fixVersion>
                                <component>couchbase-bucket</component>
                                <votes>0</votes>
                        <watches>4</watches>
                                                    <comments>
                    <comment id="23313" author="thuan" created="Thu, 29 Dec 2011 18:01:19 -0600"  >Integrated in github-ep-engine-2-0 #131 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ep-engine-2-0/131/&quot;&gt;http://qa.hq.northscale.net/job/github-ep-engine-2-0/131/&lt;/a&gt;])&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;</comment>
                    <comment id="23528" author="perry" created="Tue, 17 Jan 2012 12:58:38 -0600"  >This behavior needs to be changed.&lt;br/&gt;
&lt;br/&gt;
The current method is to use &amp;#39;-1&amp;#39; to disable the cap completely, but there are a variety of problems with that including the fact that cbflushctl can&amp;#39;t be used to actually set a -1:&lt;br/&gt;
[&lt;a href=&apos;mailto:perry@Membase1&apos;&gt;perry@Membase1&lt;/a&gt; ~]$ /opt/couchbase/bin/cbflushctl localhost:11210 set tap_throttle_queue_cap &amp;quot;-1&amp;quot;&lt;br/&gt;
usage: cbflushctl [options]&lt;br/&gt;
&lt;br/&gt;
cbflushctl: error: no such option: -1&lt;br/&gt;
&lt;br/&gt;
Please change it so that a value of &amp;#39;0&amp;#39; disables the cap</comment>
                    <comment id="23532" author="mikew" created="Tue, 17 Jan 2012 14:40:10 -0600"  >We would rather fix cbflushctl in this case since it should be able to accept negative numbers. Setting the tap_throttle_queue_cap to -1 works in ep-engine.</comment>
                    <comment id="23537" author="perry" created="Tue, 17 Jan 2012 15:54:39 -0600"  >I also tried to set it at the Erlang level with:&lt;br/&gt;
wget -O- --user=&amp;lt;user&amp;gt; --password=&amp;lt;pass&amp;gt; --post-data=&amp;#39;ns_bucket:update_bucket_props(&amp;quot;default&amp;quot;, [{extra_config_string, &amp;quot;tap_throttle_queue_cap=-1&amp;quot;}]).&amp;#39; &lt;a href=&quot;http://localhost:8091/diag/eval&quot;&gt;http://localhost:8091/diag/eval&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
And the memcached process failed to start with this message in the logs;&lt;br/&gt;
&lt;br/&gt;
[user:info] [2012-01-17 13:53:41] [&lt;a href=&apos;mailto:ns_1@127.0.0.1&apos;&gt;ns_1@127.0.0.1&lt;/a&gt;:&amp;lt;0.8646.1&amp;gt;:ns_port_server:handle_info:96] Port server memcached on node &amp;#39;&lt;a href=&apos;mailto:ns_1@127.0.0.1&apos;&gt;ns_1@127.0.0.1&lt;/a&gt;&amp;#39; exited with status 139. Restarting. Messages: Invalid entry, Key: &amp;lt;tap_throttle_queue_cap&amp;gt; Value: &amp;lt;-1&amp;gt;&lt;br/&gt;
&lt;br/&gt;
Since this works fine with a value other than -1, I assumed the problem was not just with cbflushctl...</comment>
                    <comment id="23606" author="steve" created="Thu, 19 Jan 2012 12:28:00 -0600"  >Reassigning to Jin, regarding the -1.</comment>
                    <comment id="24946" author="farshid" created="Sat, 17 Mar 2012 11:04:08 -0500"  >we should also add this to documentation.&lt;br/&gt;
adding MC to the ticket</comment>
                    <comment id="27420" author="thuan" created="Wed, 16 May 2012 18:16:19 -0500"  >Integrated in github-ep-engine-2-0 #282 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ep-engine-2-0/282/&quot;&gt;http://qa.hq.northscale.net/job/github-ep-engine-2-0/282/&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-4418&quot; title=&quot;Allow disk write queue cap to be modified at runtime&quot;&gt;&lt;strike&gt;MB-4418&lt;/strike&gt;&lt;/a&gt;: tap_throttle_queue_cap in cbflushctl takes &amp;#39;infinite&amp;#39; argument (Revision 7c4203378ab21f598247b88eefddf7d55e0bf124)&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Result = SUCCESS&lt;br/&gt;
Mike Wiederhold : &lt;br/&gt;
Files : &lt;br/&gt;
* management/cbflushctl&lt;br/&gt;
</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>Fri, 11 Nov 2011 00:37:12 -0600</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                        <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>6025</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>