<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 18 10:28:12 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-5625/MB-5625.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-5625] Rebalance can fail with various error if user changes bucket password before rebalance process</title>
                <link>http://www.couchbase.com/issues/browse/MB-5625</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>Setup: &lt;br/&gt;
1.Setup a 18 node cluster. Enable Auto-failover &lt;br/&gt;
2.Load data on all 3 buckets [around 50M, 22M, 500k] items. &lt;br/&gt;
3. Continue loading data.. &lt;br/&gt;
4. Remove orchestrator node [105] Add new node [126]&lt;br/&gt;
5. Issue rebalance on this cluster. Rebalance failed with &amp;quot;replicator died&amp;quot; - filed bug 5343&lt;br/&gt;
6. Re-issue rebalance . Rebalance fails with &amp;quot; change_filter_failed&amp;quot; &lt;br/&gt;
&lt;br/&gt;
Output:&lt;br/&gt;
Reissue rebalance fails with &amp;quot;change_filter_failed&amp;quot;&lt;br/&gt;
Node 105 is auto-failed over&lt;br/&gt;
&lt;br/&gt;
Rebalance exited with reason {{change_filter_failed,&lt;br/&gt;
{&amp;#39;EXIT&amp;#39;,&lt;br/&gt;
{{badmatch,&lt;br/&gt;
{failed,&lt;br/&gt;
{error,&lt;br/&gt;
{badmatch,&lt;br/&gt;
{memcached_error,auth_error,&lt;br/&gt;
&amp;lt;&amp;lt;&amp;quot;Auth failure&amp;quot;&amp;gt;&amp;gt;}},&lt;br/&gt;
[{ebucketmigrator_srv,connect,4},&lt;br/&gt;
{ebucketmigrator_srv,handle_call,3},&lt;br/&gt;
{gen_server,handle_msg,5},&lt;br/&gt;
{proc_lib,init_p_do_apply,3}]}}},&lt;br/&gt;
[{ns_vbm_sup,&lt;br/&gt;
&amp;#39;-local_change_vbucket_filter/4-fun-2-&amp;#39;,6},&lt;br/&gt;
{misc,&amp;#39;-executing_on_new_process/1-fun-0-&amp;#39;,&lt;br/&gt;
3}]}}},&lt;br/&gt;
[{ns_vbm_sup,change_vbucket_filter,4},&lt;br/&gt;
{ns_vbm_sup,&amp;#39;-set_replicas/3-fun-2-&amp;#39;,5},&lt;br/&gt;
{lists,foldl,3},&lt;br/&gt;
{ns_vbm_sup,set_replicas,3},&lt;br/&gt;
{ns_vbm_sup,&amp;#39;-set_replicas_on_nodes/3-fun-1-&amp;#39;,&lt;br/&gt;
3},&lt;br/&gt;
{lists,foreach,2},&lt;br/&gt;
{ns_vbm_sup,apply_changes,2},&lt;br/&gt;
{ns_vbucket_mover,sync_replicas,0}]}&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Logs at - &lt;a href=&quot;https://s3.amazonaws.com/bugdb/jira/bug4-rebalance-181/bug5.tar&quot;&gt;https://s3.amazonaws.com/bugdb/jira/bug4-rebalance-181/bug5.tar&lt;/a&gt;</description>
                <environment>Large Cluster - Centos, - 16 node cluster &lt;br/&gt;
Build 181-916rel &lt;br/&gt;
3 buckets - bucket1(3G), bucket2(2.8G), bucket3(200M)</environment>
            <key id="17913">MB-5625</key>
            <summary>Rebalance can fail with various error if user changes bucket password before rebalance process</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="6" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/closed.png">Closed</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="alkondratenko">Aleksey Kondratenko</assignee>
                                <reporter username="ketaki">Ketaki Gangal</reporter>
                        <labels>
                        <label>1.8.1-release-notes</label>
                    </labels>
                <created>Wed, 20 Jun 2012 18:25:38 -0500</created>
                <updated>Wed, 9 Jan 2013 22:59:34 -0600</updated>
                    <resolved>Tue, 31 Jul 2012 16:31:29 -0500</resolved>
                            <version>1.8.1</version>
                                <fixVersion>2.0-beta</fixVersion>
                                <component>ns_server</component>
                                <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="33126" author="farshid" created="Tue, 17 Jul 2012 13:55:33 -0500"  >changing bucket password impacts all ongoing TAP and newer connections between memcached on all nodes and changing the bucket password without re-establishing all those connections or establishing new connections without using the new password will cause those issues</comment>
                    <comment id="34050" author="perry" created="Thu, 26 Jul 2012 09:50:07 -0500"  >Just had a customer run into this...is there any workaround before the fix?  Do we know if simply retrying the rebalance will work?&lt;br/&gt;
&lt;br/&gt;
Does this mean that replication streams are stopped as well?&lt;br/&gt;
&lt;br/&gt;
What about resetting the replica chains?</comment>
                    <comment id="34422" author="peter" created="Tue, 31 Jul 2012 16:27:21 -0500"  >Alk, is this still an issue in 2.0 and if not, what is the workaround for 1.8.1? Change the password back?</comment>
                    <comment id="34423" author="alkondratenko" created="Tue, 31 Jul 2012 16:31:29 -0500"  >Doesn&amp;#39;t apply to 2.0 in 2.0 compat mode. Will still be a problem in 1.8.1 compat mode.</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, 17 Jul 2012 13:55:33 -0500</customfieldvalue>

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