<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed Jun 19 05:44:11 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-6209/MB-6209.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-6209] auto-failover should not fail over a node in the cluster if there are not enough number of replicas in the cluster</title>
                <link>http://www.couchbase.com/issues/browse/MB-6209</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>to repro : &lt;br/&gt;
&lt;br/&gt;
start from a imbalanced cluster wehre there are 1024 active vbuckets and less than 1024 vbuckets , then shut down the node and then you can see that autofailover fails over the node </description>
                <environment></environment>
            <key id="18997">MB-6209</key>
            <summary>auto-failover should not fail over a node in the cluster if there are not enough number of replicas in the cluster</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="farshid">Farshid Ghods</reporter>
                        <labels>
                        <label>customer</label>
                    </labels>
                <created>Mon, 13 Aug 2012 15:32:35 -0500</created>
                <updated>Thu, 10 Jan 2013 01:09:45 -0600</updated>
                    <resolved>Wed, 26 Sep 2012 07:59:39 -0500</resolved>
                                            <fixVersion>2.0-beta-2</fixVersion>
                                <component>ns_server</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="35325" author="farshid" created="Mon, 13 Aug 2012 15:33:10 -0500"  >reproduced this issue once on cluster_run environment with 64 vbuckets , will try on a cluster and attach diags.</comment>
                    <comment id="36317" author="farshid" created="Tue, 21 Aug 2012 12:31:58 -0500"  >Hi Aliaksey,&lt;br/&gt;
&lt;br/&gt;
can you please merge this fix to 1.8.1 branch ? </comment>
                    <comment id="39705" author="alkondratenko" created="Wed, 26 Sep 2012 07:59:39 -0500"  >Fix is in gerrit</comment>
                    <comment id="42654" author="kzeller" created="Fri, 26 Oct 2012 18:08:17 -0500"  >in RN: When you try to automatically failover a node, Couchbase Server &lt;br/&gt;
will not perform the failover if there are not enough &lt;br/&gt;
replica nodes in the cluster to support the failed node.</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>Wed, 26 Sep 2012 07:59:39 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>4400</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                                                <customfield id="customfield_10052" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Sprint Status</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10027"><![CDATA[Current Sprint]]></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>