<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 18 11:10: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-7383/MB-7383.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-7383] active item resident ratio drop significantly when adding a 2.0 node to 1.8.1 cluster for upgrade ( sasl bucket )</title>
                <link>http://www.couchbase.com/issues/browse/MB-7383</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>scenario:&lt;br/&gt;
add 2x2.0 nodes to a 3 node cluster with 2 buckets ( default and sasl where active resident ration is 60% )  few minutes after upgrade process begins active item ration on 10.3.2.43 which is an existing 1.8.1 node , drops from 60% -&amp;gt; 58-&amp;gt;48-&amp;gt;38-15-&amp;gt;5 and then we decided to stop rebalance&lt;br/&gt;
&lt;br/&gt;
i grabbed diags from the node which resident ratio dropped from 63 percent to 5 percent.&lt;br/&gt;
&lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/systemtest/resident-ratio-drop-2853bb89.zip&quot;&gt;https://s3.amazonaws.com/bugdb/jira/systemtest/resident-ratio-drop-2853bb89.zip&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
please open a bug asap and mention this there. assign the bug to chiyoung and hoping that he or mike can take a look at the cluster.&lt;br/&gt;
&lt;br/&gt;
[stats:debug] [2012-12-08 17:43:52]&lt;br/&gt;
active item resident ratio is at 63% and everything looks normal&lt;br/&gt;
&lt;br/&gt;
and then at &lt;br/&gt;
[stats:debug] [2012-12-08 17:45:32]&lt;br/&gt;
vb_active_perc_mem_resident   58&lt;br/&gt;
&lt;br/&gt;
and at &lt;br/&gt;
[stats:debug] [2012-12-08 17:47:12]&lt;br/&gt;
vb_active_perc_mem_resident   49&lt;br/&gt;
&lt;br/&gt;
and at &lt;br/&gt;
[stats:debug] [2012-12-08 18:03:51]&lt;br/&gt;
vb_active_perc_mem_resident   35&lt;br/&gt;
&lt;br/&gt;
what has happened between 17:45 and 17:47 or between 17:56 and 18:03 that pushed the resident ratio this low.&lt;br/&gt;
whatever it is there is a combination of 1.8.1 and 2.0 that is causing the issue&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
collect info from other nodes:&lt;br/&gt;
&lt;br/&gt;
</description>
                <environment></environment>
            <key id="21219">MB-7383</key>
            <summary>active item resident ratio drop significantly when adding a 2.0 node to 1.8.1 cluster for upgrade ( sasl bucket )</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="5">Cannot Reproduce</resolution>
                    <security id="10011">Public</security>
                        <assignee username="Chisheng">Chisheng Hong</assignee>
                                <reporter username="farshid">Farshid Ghods</reporter>
                        <labels>
                        <label>2.0.0-hotfix</label>
                    </labels>
                <created>Sun, 9 Dec 2012 18:07:26 -0600</created>
                <updated>Wed, 2 Jan 2013 11:57:19 -0600</updated>
                    <resolved>Thu, 27 Dec 2012 19:12:43 -0600</resolved>
                            <version>2.0</version>
                                <fixVersion>2.0.1</fixVersion>
                                <component>couchbase-bucket</component>
                                <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="45681" author="farshid" created="Sun, 9 Dec 2012 18:17:27 -0600"  >existing 1.8.1 node : &lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.122-1292012-1553-diag.zip&quot;&gt;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.122-1292012-1553-diag.zip&lt;/a&gt;&lt;br/&gt;
2.0 node : &lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.41-1292012-161-diag.zip&quot;&gt;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.41-1292012-161-diag.zip&lt;/a&gt;&lt;br/&gt;
existing 1.8.1 node : &lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.43-1292012-1551-diag.zip&quot;&gt;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.43-1292012-1551-diag.zip&lt;/a&gt; &lt;br/&gt;
existing 1.8.1 node :  &lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.47-1292012-1558-diag.zip&quot;&gt;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.47-1292012-1558-diag.zip&lt;/a&gt;</comment>
                    <comment id="45682" author="farshid" created="Sun, 9 Dec 2012 18:21:50 -0600"  >2.0 node : 10.3.2.85 &lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.85-1292012-1616-diag.zip&quot;&gt;https://s3.amazonaws.com/bugdb/jira/MB-7383/10.3.2.85-1292012-1616-diag.zip&lt;/a&gt;</comment>
                    <comment id="45685" author="chiyoung" created="Sun, 9 Dec 2012 19:29:16 -0600"  >Farshid,&lt;br/&gt;
&lt;br/&gt;
This might be caused by the memory leak bug in 1.8.1. Can you please test it with the latest 1.8.1 patch (build 943?)?</comment>
                    <comment id="45686" author="farshid" created="Mon, 10 Dec 2012 00:16:39 -0600"  >from the email&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Chisheng,&lt;br/&gt;
&lt;br/&gt;
Lets patch the ep.so file from the one which is available from 1.8.1-943-rel build and apply it to all nodes in this cluster , then add another 2.0 node and rebalance the cluster again&lt;br/&gt;
&lt;br/&gt;
Please keep chiyoung in the loop after the experiment.</comment>
                    <comment id="45687" author="farshid" created="Mon, 10 Dec 2012 00:17:23 -0600"  >QE will update the ticket when results are available</comment>
                    <comment id="46649" author="Chisheng" created="Thu, 27 Dec 2012 19:12:36 -0600"  >&lt;a href=&quot;https://github.com/couchbaselabs/couchbase-qe-docs/blob/master/system-tests/pine-cluster/12-10-2012.txt&quot;&gt;https://github.com/couchbaselabs/couchbase-qe-docs/blob/master/system-tests/pine-cluster/12-10-2012.txt&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
Can not repro this on EC2 cluster for Centos. This problem is caused by slow disk speed in previous test: &lt;a href=&quot;https://github.com/couchbaselabs/couchbase-qe-docs/blob/master/system-tests/pine-cluster/12-08-2012.txt&quot;&gt;https://github.com/couchbaselabs/couchbase-qe-docs/blob/master/system-tests/pine-cluster/12-08-2012.txt&lt;/a&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>Sun, 9 Dec 2012 19:29:16 -0600</customfieldvalue>

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