<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 25 16:55:20 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-6974/MB-6974.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-6974] erlang FULL_SWEEP setting needs override to 512 instead of erlang&apos;s default</title>
                <link>http://www.couchbase.com/issues/browse/MB-6974</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>Looks like 512 is the better setting than the default...&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&lt;a href=&quot;https://docs.google.com/spreadsheet/ccc?key=0AgLUessE73UXdGd2NmhLOThCRUc0ekFkZ0FDeGdLRXc#gid=0&quot;&gt;https://docs.google.com/spreadsheet/ccc?key=0AgLUessE73UXdGd2NmhLOThCRUc0ekFkZ0FDeGdLRXc#gid=0&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
</description>
                <environment></environment>
            <key id="20333">MB-6974</key>
            <summary>erlang FULL_SWEEP setting needs override to 512 instead of erlang&apos;s default</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="1" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/blocker.png">Blocker</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="alkondratenko">Aleksey Kondratenko</assignee>
                                <reporter username="steve">Steve Yen</reporter>
                        <labels>
                    </labels>
                <created>Fri, 19 Oct 2012 13:03:53 -0500</created>
                <updated>Mon, 12 Nov 2012 15:09:32 -0600</updated>
                    <resolved>Tue, 23 Oct 2012 19:42:24 -0500</resolved>
                            <version>2.0-beta</version>
                                <fixVersion>2.0-beta-2</fixVersion>
                                <component>ns_server</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="41982" author="steve" created="Fri, 19 Oct 2012 14:49:27 -0500"  >Changing title to be clearer.&lt;br/&gt;
&lt;br/&gt;
Also, I spoke with Damien and he&amp;#39;s good with 512, too.</comment>
                    <comment id="41988" author="pavelpaulau" created="Fri, 19 Oct 2012 16:37:44 -0500"  >You don&amp;#39;t wait for system test results? You don&amp;#39;t need extra perf runs for that?</comment>
                    <comment id="41991" author="alkondratenko" created="Fri, 19 Oct 2012 16:47:01 -0500"  >We can always revert later. But I&amp;#39;d wait at least a bit.</comment>
                    <comment id="42186" author="farshid" created="Mon, 22 Oct 2012 08:46:55 -0500"  >Tommie,&lt;br/&gt;
&lt;br/&gt;
can you update the ticket once you have initial results from pine and plum cluster where we are running the cluster with this settings ?</comment>
                    <comment id="42189" author="tommie" created="Mon, 22 Oct 2012 10:25:58 -0500"  >Current status of verification on key-value and query clusters:&lt;br/&gt;
&amp;nbsp;&lt;br/&gt;
Overall looks good on 23 node with key-value workload with SWEEP=512:&lt;br/&gt;
&amp;nbsp;* load 20 Million items, size 356bytes&lt;br/&gt;
&amp;nbsp;* access phase: --get 70% --create 10% --update 15% --delete 5%  --ops 40000 &lt;br/&gt;
&amp;nbsp;* rebalance out 3 nodes completed&lt;br/&gt;
&amp;nbsp;* load until 44% active resident&lt;br/&gt;
&amp;nbsp;* access phase with cache_miss ratio between 1-3%&lt;br/&gt;
&amp;nbsp;* swap rebalance in 3 nodes, out 3 nodes  completed&lt;br/&gt;
&lt;br/&gt;
Timeouts on 4 node cluster with views and SWEEP=10000:&lt;br/&gt;
&amp;nbsp;&amp;nbsp;* load 13 million items into 2 different buckets&lt;br/&gt;
&amp;nbsp;&amp;nbsp;* run 300/queries-per-sec against each bucket&lt;br/&gt;
&amp;nbsp;&amp;nbsp;* access phase at 70% active resident&lt;br/&gt;
&amp;nbsp;&amp;nbsp;* rebalance out 1 node  &lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- Failed with etimeout&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;- usually able to retry and will succeed&lt;br/&gt;
&lt;br/&gt;
On 4 node cluster with views and SWEEP=512:&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;* verification pending...</comment>
                    <comment id="42313" author="steve" created="Tue, 23 Oct 2012 14:44:56 -0500"  >assigning back to alk to get the 512 setting changed.</comment>
                    <comment id="42320" author="tommie" created="Tue, 23 Oct 2012 16:06:16 -0500"  >&lt;br/&gt;
Recent system test verification failed due to another issue &lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-6490&quot; title=&quot;Rebalance failed with reason &amp;quot;Partition 687 not in active nor passive set&amp;quot; in add in node rebalance&quot;&gt;&lt;strike&gt;MB-6490&lt;/strike&gt;&lt;/a&gt;&#8230;.Instead of the timeouts we saw at higher gc levels.</comment>
                    <comment id="42335" author="steve" created="Tue, 23 Oct 2012 18:32:05 -0500"  >changing priority to blocker (from critical)</comment>
                    <comment id="42352" author="alkondratenko" created="Tue, 23 Oct 2012 19:42:24 -0500"  >Change is in gerrit and will be merged soon</comment>
                    <comment id="42357" author="steve" created="Tue, 23 Oct 2012 20:18:24 -0500"  >Aliaksey A. had a good point on the fix, where we need a corresponding fix for the windows?</comment>
                    <comment id="43828" author="kzeller" created="Mon, 12 Nov 2012 15:09:32 -0600"  >added to RN: By default we provide garbage collection more frequently than the &lt;br/&gt;
normal default for Erlang. This keeps memory usage by the Erlang &lt;br/&gt;
virtual machine lower, and enables better performance.</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, 19 Oct 2012 16:37:44 -0500</customfieldvalue>

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