<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 05:57:03 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-4756/MB-4756.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-4756] If Fail Over is in progress and node goes offline, UI looks/acts strangely</title>
                <link>http://www.couchbase.com/issues/browse/MB-4756</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>It seems the JS for this section is prioritizing the fact that the node was going to be failed over above the fact that the node is no longer available.&lt;br/&gt;
&lt;br/&gt;
I&amp;#39;m not sure what the server-side logic relationship is in this situation, but hopefully it&amp;#39;s just a matter of re-prioritizing some conditions in the UI JS.</description>
                <environment></environment>
            <key id="16077">MB-4756</key>
            <summary>If Fail Over is in progress and node goes offline, UI looks/acts strangely</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="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="pavel">Pavel Blagodov</assignee>
                                <reporter username="BigBlueHat">Benjamin Young</reporter>
                        <labels>
                        <label>customer</label>
                    </labels>
                <created>Fri, 3 Feb 2012 09:24:37 -0600</created>
                <updated>Fri, 7 Sep 2012 00:25:07 -0500</updated>
                    <resolved>Wed, 29 Aug 2012 05:15:21 -0500</resolved>
                            <version>2.0-developer-preview-3</version>
                <version>2.0-developer-preview-4</version>
                                <fixVersion>2.0-beta</fixVersion>
                                <component>ns_server</component>
                <component>UI</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="24056" author="alkondratenko" created="Fri, 3 Feb 2012 09:54:00 -0600"  >I need more details</comment>
                    <comment id="24075" author="BigBlueHat" created="Fri, 3 Feb 2012 15:29:24 -0600"  >./cluster_run -n 2 --host=127.0.0.1&lt;br/&gt;
./cluster_connect -n 2&lt;br/&gt;
&lt;br/&gt;
Then, in the UI, click &amp;quot;Fail Over&amp;quot; for one of the nodes.&lt;br/&gt;
&lt;br/&gt;
Then Ctrl+C your ./cluster_run process, and restart it with&lt;br/&gt;
./cluster_run -n 1 --host=127.0.0.1&lt;br/&gt;
&lt;br/&gt;
Reload the Server List screen.&lt;br/&gt;
&lt;br/&gt;
I&amp;#39;ll upload screenshots shortly.&lt;br/&gt;
</comment>
                    <comment id="24077" author="BigBlueHat" created="Fri, 3 Feb 2012 15:32:12 -0600"  >Active Servers list with the node marked for &amp;quot;Fail Over&amp;quot; after it&amp;#39;s been taken &amp;quot;forcably&amp;quot; offline prior to rebalancing.</comment>
                    <comment id="24078" author="BigBlueHat" created="Fri, 3 Feb 2012 15:32:50 -0600"  >Pending Rebalance scenario.</comment>
                    <comment id="24079" author="alkondratenko" created="Fri, 3 Feb 2012 15:42:32 -0600"  >so weird thing is NaN? I don&amp;#39;t see anything else there</comment>
                    <comment id="24081" author="BigBlueHat" created="Fri, 3 Feb 2012 16:05:34 -0600"  >The servers down, not pending. The host name is missing from the Pending Rebalance list.</comment>
                    <comment id="24082" author="alkondratenko" created="Fri, 3 Feb 2012 16:16:32 -0600"  >so two bugs. First that pending is somehow used. We have ongoing work to untangle node&amp;#39;s health and it&amp;#39;s warmup status.&lt;br/&gt;
&lt;br/&gt;
Second is that name is missing in second tab. Thanks for finding it.</comment>
                    <comment id="36427" author="alkondratenko" created="Tue, 21 Aug 2012 20:32:04 -0500"  >May be partly fixed already</comment>
                    <comment id="37216" author="pavel" created="Wed, 29 Aug 2012 05:15:21 -0500"  >&lt;a href=&quot;http://review.couchbase.org/20298&quot;&gt;http://review.couchbase.org/20298&lt;/a&gt;</comment>
                    <comment id="37978" author="thuan" created="Fri, 7 Sep 2012 00:25:07 -0500"  >Integrated in github-ns-server-2-0 #461 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ns-server-2-0/461/&quot;&gt;http://qa.hq.northscale.net/job/github-ns-server-2-0/461/&lt;/a&gt;])&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-4756&quot; title=&quot;If Fail Over is in progress and node goes offline, UI looks/acts strangely&quot;&gt;&lt;strike&gt;MB-4756&lt;/strike&gt;&lt;/a&gt;: fixed server down state (Revision 5ec376241ca924ccc8d45b214c50d9daf64901bb)&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Result = SUCCESS&lt;br/&gt;
pwansch : &lt;br/&gt;
Files : &lt;br/&gt;
* priv/public/js/core-data.js&lt;br/&gt;
* priv/public/index.html&lt;br/&gt;
</comment>
                </comments>
                    <attachments>
                    <attachment id="12185" name="Screen shot 2012-02-03 at 10.19.02 AM.png" size="46636" author="BigBlueHat" created="Fri, 3 Feb 2012 15:32:12 -0600" />
                    <attachment id="12186" name="Screen shot 2012-02-03 at 10.19.07 AM.png" size="35731" author="BigBlueHat" created="Fri, 3 Feb 2012 15:32:50 -0600" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Fri, 3 Feb 2012 09:54:00 -0600</customfieldvalue>

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