<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 18 21:04:32 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-3423/MB-3423.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-3423] &apos;ejectNode&apos; is possibly destructive to data</title>
                <link>http://www.couchbase.com/issues/browse/MB-3423</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>The current implementation of &amp;#39;ejectNode&amp;#39; can be possibly destructive to data if it is run against a node that is in the cluster and responsible for vbuckets.&lt;br/&gt;
&amp;nbsp;We need to a) update the REST API documentation to describe specifically what it is to be used for and b) not allow ejectNode to be run on a node that is serving data  &lt;br/&gt;
&lt;br/&gt;
If absolutely necessary, a &amp;#39;force&amp;#39; option could be implemented to allow ejection of an active node, but I don&amp;#39;t think it&amp;#39;s needed at this time.</description>
                <environment></environment>
            <key id="13524">MB-3423</key>
            <summary>&apos;ejectNode&apos; is possibly destructive to data</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="alkondratenko">Aleksey Kondratenko</assignee>
                                <reporter username="perry">Perry Krug</reporter>
                        <labels>
                        <label>1.6.0-release-notes</label>
                        <label>1.6.5.3-release-notes</label>
                        <label>1.7.0-release-notes</label>
                        <label>1.7.1-release-notes</label>
                    </labels>
                <created>Mon, 7 Feb 2011 19:04:18 -0600</created>
                <updated>Tue, 21 Aug 2012 19:19:26 -0500</updated>
                    <resolved>Tue, 21 Aug 2012 19:19:26 -0500</resolved>
                            <version>1.6.5</version>
                                                <component>RESTful-APIs</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="20635" author="perry" created="Tue, 10 May 2011 17:44:45 -0500"  >A Pivotal Tracker story has been created for this Issue: &lt;a href=&quot;http://www.pivotaltracker.com/story/show/13245397&quot;&gt;http://www.pivotaltracker.com/story/show/13245397&lt;/a&gt;</comment>
                    <comment id="21081" author="farshid" created="Sat, 4 Jun 2011 19:06:03 -0500"  >I am not sure why this issue is marked as a release note.&lt;br/&gt;
&lt;br/&gt;
this is a side effect of using ejectNode api which is based on the design and the user need to be aware of when and how they using this rest api call.</comment>
                    <comment id="21089" author="perry" created="Sun, 5 Jun 2011 20:48:40 -0500"  >It&amp;#39;s a release note because I believe the user needs to be aware that this would cause bad things to happen if done improperly.  Until we either update the documentation or prevent the user from doing this, I think it&amp;#39;s non-obvious and therefore requires a release note.</comment>
                    <comment id="28713" author="farshid" created="Sun, 3 Jun 2012 17:51:26 -0500"  >can we close this as won&amp;#39;t fix ?</comment>
                    <comment id="36397" author="alkondratenko" created="Tue, 21 Aug 2012 19:19:26 -0500"  >already done apparently&lt;br/&gt;
&lt;br/&gt;
# wget -O- -d --user=Administrator --password=asdasd --post-data=&amp;quot;otpNode=n_0@10.17.20.233&amp;quot; &lt;a href=&quot;http://lh:9000/controller/ejectNode&quot;&gt;http://lh:9000/controller/ejectNode&lt;/a&gt;&lt;br/&gt;
Setting --user (user) to Administrator&lt;br/&gt;
Setting --password (password) to asdasd&lt;br/&gt;
Setting --post-data (postdata) to otpNode=n_0@10.17.20.233&lt;br/&gt;
DEBUG output created by Wget 1.14 on linux-gnu.&lt;br/&gt;
&lt;br/&gt;
URI encoding = &#8216;UTF-8&#8217;&lt;br/&gt;
--2012-08-21 17:19:01--  &lt;a href=&quot;http://lh:9000/controller/ejectNode&quot;&gt;http://lh:9000/controller/ejectNode&lt;/a&gt;&lt;br/&gt;
Host &#8216;lh&#8217; has not issued a general basic challenge.&lt;br/&gt;
Resolving lh (lh)... 127.0.0.1&lt;br/&gt;
Caching lh =&amp;gt; 127.0.0.1&lt;br/&gt;
Connecting to lh (lh)|127.0.0.1|:9000... connected.&lt;br/&gt;
Created socket 3.&lt;br/&gt;
Releasing 0x09cb2f48 (new refcount 1).&lt;br/&gt;
&lt;br/&gt;
---request begin---&lt;br/&gt;
POST /controller/ejectNode HTTP/1.1&lt;br/&gt;
User-Agent: Wget/1.14 (linux-gnu)&lt;br/&gt;
Accept: */*&lt;br/&gt;
Host: lh:9000&lt;br/&gt;
Connection: Keep-Alive&lt;br/&gt;
Content-Type: application/x-www-form-urlencoded&lt;br/&gt;
Content-Length: 24&lt;br/&gt;
&lt;br/&gt;
---request end---&lt;br/&gt;
[POST data: otpNode=n_0@10.17.20.233]&lt;br/&gt;
HTTP request sent, awaiting response... &lt;br/&gt;
---response begin---&lt;br/&gt;
HTTP/1.1 401 Unauthorized&lt;br/&gt;
WWW-Authenticate: Basic realm=&amp;quot;Couchbase Server Admin / REST&amp;quot;&lt;br/&gt;
Server: Couchbase Server 2.0.0r_231_gdcd71d5&lt;br/&gt;
Pragma: no-cache&lt;br/&gt;
Date: Wed, 22 Aug 2012 00:19:01 GMT&lt;br/&gt;
Content-Length: 0&lt;br/&gt;
Cache-Control: no-cache&lt;br/&gt;
&lt;br/&gt;
---response end---&lt;br/&gt;
401 Unauthorized&lt;br/&gt;
Registered socket 3 for persistent reuse.&lt;br/&gt;
] done.&lt;br/&gt;
Inserted &#8216;lh&#8217; into basic_authed_hosts&lt;br/&gt;
Disabling further reuse of socket 3.&lt;br/&gt;
Closed fd 3&lt;br/&gt;
&lt;br/&gt;
---request begin---&lt;br/&gt;
POST /controller/ejectNode HTTP/1.1&lt;br/&gt;
User-Agent: Wget/1.14 (linux-gnu)&lt;br/&gt;
Accept: */*&lt;br/&gt;
Host: lh:9000&lt;br/&gt;
Connection: Keep-Alive&lt;br/&gt;
Content-Type: application/x-www-form-urlencoded&lt;br/&gt;
Content-Length: 24&lt;br/&gt;
Authorization: Basic QWRtaW5pc3RyYXRvcjphc2Rhc2Q=&lt;br/&gt;
&lt;br/&gt;
---request end---&lt;br/&gt;
Failed writing HTTP request: Bad file descriptor.&lt;br/&gt;
Closed fd 3&lt;br/&gt;
Retrying.&lt;br/&gt;
&lt;br/&gt;
--2012-08-21 17:19:02--  (try: 2)  &lt;a href=&quot;http://lh:9000/controller/ejectNode&quot;&gt;http://lh:9000/controller/ejectNode&lt;/a&gt;&lt;br/&gt;
Found &#8216;lh&#8217; in basic_authed_hosts.&lt;br/&gt;
Found lh in host_name_addresses_map (0x9cb2f48)&lt;br/&gt;
Connecting to lh (lh)|127.0.0.1|:9000... connected.&lt;br/&gt;
Created socket 3.&lt;br/&gt;
Releasing 0x09cb2f48 (new refcount 1).&lt;br/&gt;
&lt;br/&gt;
---request begin---&lt;br/&gt;
POST /controller/ejectNode HTTP/1.1&lt;br/&gt;
User-Agent: Wget/1.14 (linux-gnu)&lt;br/&gt;
Accept: */*&lt;br/&gt;
Authorization: Basic QWRtaW5pc3RyYXRvcjphc2Rhc2Q=&lt;br/&gt;
Host: lh:9000&lt;br/&gt;
Connection: Keep-Alive&lt;br/&gt;
Content-Type: application/x-www-form-urlencoded&lt;br/&gt;
Content-Length: 24&lt;br/&gt;
&lt;br/&gt;
---request end---&lt;br/&gt;
[POST data: otpNode=n_0@10.17.20.233]&lt;br/&gt;
HTTP request sent, awaiting response... &lt;br/&gt;
---response begin---&lt;br/&gt;
HTTP/1.1 400 Bad Request&lt;br/&gt;
Server: Couchbase Server 2.0.0r_231_gdcd71d5&lt;br/&gt;
Pragma: no-cache&lt;br/&gt;
Date: Wed, 22 Aug 2012 00:19:02 GMT&lt;br/&gt;
Content-Length: 29&lt;br/&gt;
Cache-Control: no-cache&lt;br/&gt;
&lt;br/&gt;
---response end---&lt;br/&gt;
400 Bad Request&lt;br/&gt;
Registered socket 3 for persistent reuse.&lt;br/&gt;
Skipping 29 bytes of body: [Cannot remove active server.&lt;br/&gt;
] done.&lt;br/&gt;
2012-08-21 17:19:02 ERROR 400: Bad Request.&lt;br/&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>Sat, 4 Jun 2011 19:06:03 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10010" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                <customfieldname>Flagged</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10010"><![CDATA[Release Note]]></customfieldvalue>
    
                </customfieldvalues>
            </customfield>
                                                                                                                                                <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>1904</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>