<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 25 03:41:18 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-7290/MB-7290.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-7290] Rebalance-in operation failed twice with &quot;bulk_set_vbucket_state&quot; failing with heavy front end load on an XDCR set up and with system in DGM (~65% resident ratio)</title>
                <link>http://www.couchbase.com/issues/browse/MB-7290</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>At the time of the rebalance failure:&lt;br/&gt;
&lt;br/&gt;
+ 5 nodes rebalance in on each cluster &lt;br/&gt;
Cluster setup: c1:c2::10:10 &lt;br/&gt;
biXDCR_bucket: c1 &amp;lt;---&amp;gt; c2 &lt;br/&gt;
uniXDCR_src: c1 ---&amp;gt; c2 :uniXDCR_dest &lt;br/&gt;
Front end loads on c1 and c2 for biXDCR_bucket, and on c1 for uniXDCR_src. &lt;br/&gt;
c1: &lt;a href=&quot;http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/&quot;&gt;http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/&lt;/a&gt; &lt;br/&gt;
c2: &lt;a href=&quot;http://ec2-175-41-186-167.ap-southeast-1.compute.amazonaws.com:8091/&quot;&gt;http://ec2-175-41-186-167.ap-southeast-1.compute.amazonaws.com:8091/&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
On C1, Rebalance operation failed with this reason on the UI logs:&lt;br/&gt;
&lt;br/&gt;
Rebalance exited with reason {{bulk_set_vbucket_state_failed,&lt;br/&gt;
[{&amp;#39;&lt;a href=&apos;mailto:ns_1@ec2-177-71-170-44.sa-east-1.compute.amazonaws.com&apos;&gt;ns_1@ec2-177-71-170-44.sa-east-1.compute.amazonaws.com&lt;/a&gt;&amp;#39;,&lt;br/&gt;
{&amp;#39;EXIT&amp;#39;,&lt;br/&gt;
{{timeout,&lt;br/&gt;
{gen_server,call,&lt;br/&gt;
[&amp;#39;ns_memcached-biXDCR_bucket&amp;#39;,&lt;br/&gt;
{set_vbucket,544,replica},&lt;br/&gt;
180000]}},&lt;br/&gt;
{gen_server,call,&lt;br/&gt;
[{&amp;#39;janitor_agent-biXDCR_bucket&amp;#39;,&lt;br/&gt;
&amp;#39;&lt;a href=&apos;mailto:ns_1@ec2-177-71-170-44.sa-east-1.compute.amazonaws.com&apos;&gt;ns_1@ec2-177-71-170-44.sa-east-1.compute.amazonaws.com&lt;/a&gt;&amp;#39;},&lt;br/&gt;
{if_rebalance,&amp;lt;0.10136.88&amp;gt;,&lt;br/&gt;
{update_vbucket_state,544,replica,&lt;br/&gt;
undefined,undefined}},&lt;br/&gt;
infinity]}}}}]},&lt;br/&gt;
[{janitor_agent,bulk_set_vbucket_state,4},&lt;br/&gt;
{ns_vbucket_mover,&lt;br/&gt;
update_replication_post_move,3},&lt;br/&gt;
{ns_vbucket_mover,handle_info,2},&lt;br/&gt;
{gen_server,handle_msg,5},&lt;br/&gt;
{proc_lib,init_p_do_apply,3}]}&lt;br/&gt;
&lt;br/&gt;
The second time, rebalance failed with the following UI log message:&lt;br/&gt;
&lt;br/&gt;
Rebalance exited with reason {{timeout,&lt;br/&gt;
{gen_server,call,&lt;br/&gt;
[&amp;#39;ns_memcached-biXDCR_bucket&amp;#39;,&lt;br/&gt;
{set_vbucket,849,active},&lt;br/&gt;
180000]}},&lt;br/&gt;
{gen_server,call,&lt;br/&gt;
[{&amp;#39;janitor_agent-biXDCR_bucket&amp;#39;,&lt;br/&gt;
&amp;#39;&lt;a href=&apos;mailto:ns_1@ec2-177-71-230-72.sa-east-1.compute.amazonaws.com&apos;&gt;ns_1@ec2-177-71-230-72.sa-east-1.compute.amazonaws.com&lt;/a&gt;&amp;#39;},&lt;br/&gt;
{if_rebalance,&amp;lt;0.21090.114&amp;gt;,&lt;br/&gt;
{update_vbucket_state,849,active,paused,&lt;br/&gt;
undefined}},&lt;br/&gt;
infinity]}}&lt;br/&gt;
&lt;br/&gt;
After giving it some time, the third rebalance did complete successfully.&lt;br/&gt;
&lt;br/&gt;
Will attach the grabbed diags from one of the nodes at C1 in a bit.</description>
                <environment>- 5:5 uni &amp;amp; bidirectional XDCR &lt;br/&gt;
- ec2 nodes with 15G RAM &lt;br/&gt;
- 12.04 Ubuntu LTS &lt;br/&gt;
- 400G disk space on each node &lt;br/&gt;
- &lt;a href=&quot;http://builds.hq.northscale.net/latestbuilds/couchbase-server-enterprise_x86_64_2.0.0-1967-rel.deb.manifest.xml&quot;&gt;http://builds.hq.northscale.net/latestbuilds/couchbase-server-enterprise_x86_64_2.0.0-1967-rel.deb.manifest.xml&lt;/a&gt;</environment>
            <key id="21006">MB-7290</key>
            <summary>Rebalance-in operation failed twice with &quot;bulk_set_vbucket_state&quot; failing with heavy front end load on an XDCR set up and with system in DGM (~65% resident ratio)</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</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="5">Cannot Reproduce</resolution>
                    <security id="10011">Public</security>
                        <assignee username="mikew">Mike Wiederhold</assignee>
                                <reporter username="abhinav">Abhinav Dangeti</reporter>
                        <labels>
                        <label>2.0-release-notes</label>
                    </labels>
                <created>Thu, 29 Nov 2012 13:18:30 -0600</created>
                <updated>Wed, 10 Apr 2013 15:12:09 -0500</updated>
                    <resolved>Wed, 10 Apr 2013 15:12:09 -0500</resolved>
                            <version>2.0</version>
                                <fixVersion>2.1</fixVersion>
                                <component>couchbase-bucket</component>
                <component>ns_server</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="45017" author="abhinav" created="Thu, 29 Nov 2012 13:21:34 -0600"  >Grabbed diags from C1&amp;#39;s ec2-177-71-230-72.sa-east-1.compute.amazonaws.com :-&lt;br/&gt;
&lt;a href=&quot;https://s3.amazonaws.com/bugdb/MB-7290/ec2-177-71-230-72.sa-east-1.compute.amazonaws.com-8091-diag.txt.gz&quot;&gt;https://s3.amazonaws.com/bugdb/MB-7290/ec2-177-71-230-72.sa-east-1.compute.amazonaws.com-8091-diag.txt.gz&lt;/a&gt;</comment>
                    <comment id="45032" author="junyi" created="Thu, 29 Nov 2012 15:02:03 -0600"  >Abhinav,  the error was raised when ns_server is trying to set vbucket state during rebalance under heavy workload. Please talk to ns_server team. Thanks.</comment>
                    <comment id="45033" author="junyi" created="Thu, 29 Nov 2012 15:02:34 -0600"  >Please assign to ns_server team.</comment>
                    <comment id="45236" author="alkondratenko" created="Mon, 3 Dec 2012 12:24:13 -0600"  >Please explain what exactly is needed here from me. Looks like ordinary timeout. Memcached timeout in fact (3 minutes is no joke).</comment>
                    <comment id="45238" author="farshid" created="Mon, 3 Dec 2012 12:27:26 -0600"  >filing this under memcached timeouts then</comment>
                    <comment id="45490" author="kzeller" created="Wed, 5 Dec 2012 14:06:34 -0600"  >&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Added to RN:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;Under a heavy load of write operations on two clusters and both &lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;bi-directional and uni-directional replications occurring &lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;via XDCR, Couchbase Server 2.0 may fail during rebalance.</comment>
                    <comment id="45631" author="junyi" created="Thu, 6 Dec 2012 19:07:22 -0600"  >it has nothing to do with XDCR core code, remove xdcr from the component. </comment>
                    <comment id="45701" author="farshid" created="Mon, 10 Dec 2012 11:30:19 -0600"  >deferring to 2.1 per bug scrub meeting ( Dipti &amp;amp; Farshid -December 7th )</comment>
                    <comment id="50627" author="chiyoung" created="Fri, 15 Feb 2013 19:17:21 -0600"  >For the bug distributions in the engine team.</comment>
                    <comment id="54804" author="mikew" created="Wed, 10 Apr 2013 15:12:09 -0500"  >This issue is 5 months old. Please open a new issue against the latest build if you see this issue again.</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>Thu, 29 Nov 2012 15:02:03 -0600</customfieldvalue>

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