<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 20:31:09 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-4564/MB-4564.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-4564] Don&apos;t delete database files when node leaves cluster.</title>
                <link>http://www.couchbase.com/issues/browse/MB-4564</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>A recent bug brought up a concern around the process of deleting the on-disk data files when a node is failed over or removed from the cluster.&lt;br/&gt;
&lt;br/&gt;
I think it would be a better approach to preserve this data in the event that it is needed.  Perhaps moving them out of the way and messaging to the user that they can clean them up manually when needed.</description>
                <environment></environment>
            <key id="15732">MB-4564</key>
            <summary>Don&apos;t delete database files when node leaves cluster.</summary>
                <type id="4" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="1" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/blocker.png">Blocker</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="Aliaksey Artamonau">Aliaksey Artamonau</assignee>
                                <reporter username="perry">Perry Krug</reporter>
                        <labels>
                        <label>1.8.1-release-notes</label>
                        <label>customer</label>
                    </labels>
                <created>Wed, 21 Dec 2011 14:02:53 -0600</created>
                <updated>Sun, 13 May 2012 18:32:08 -0500</updated>
                    <resolved>Mon, 9 Apr 2012 21:12:13 -0500</resolved>
                            <version>1.7.2</version>
                                <fixVersion>1.8.1</fixVersion>
                                <component>ns_server</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="23910" author="alkondratenko" created="Mon, 30 Jan 2012 16:34:04 -0600"  >Perry, you want files preserved for eternity or we can/should get rid of them when node is re-initialized or joins some cluster ?</comment>
                    <comment id="23913" author="perry" created="Mon, 30 Jan 2012 16:52:14 -0600"  >I think the join cluster could be a fine situation to clean them up. What do you mean by re-initialized?  This is really only needed as a fail-safe situation in case we need to recover the data from the node that was failed over or removed.</comment>
                    <comment id="23914" author="alkondratenko" created="Mon, 30 Jan 2012 16:57:49 -0600"  >that&amp;#39;s when/if node is initialized via setup wizard as standalone cluster</comment>
                    <comment id="23918" author="perry" created="Mon, 30 Jan 2012 17:21:53 -0600"  >Oh, yes...then that&amp;#39;s a good time as well too.  My only concern would be that the current code path re-initializes the node when it gets failed over or removed so we&amp;#39;d have to change that behavior.</comment>
                    <comment id="25376" author="steve" created="Fri, 30 Mar 2012 15:47:23 -0500"  >Aliaksey still needs final requirements on how this needs to behave.</comment>
                    <comment id="25451" author="steve" created="Tue, 3 Apr 2012 16:45:06 -0500"  >Please document decision here.</comment>
                    <comment id="25563" author="alkondratenko" created="Sat, 7 Apr 2012 18:15:19 -0500"  >Aliaksey took this.&lt;br/&gt;
&lt;br/&gt;
Decision was to don&amp;#39;t touch files when node is ejected/failed over. But rid of them either in the middle of wizard or when rebalance back in starts.&lt;br/&gt;
</comment>
                    <comment id="25570" author="perry" created="Mon, 9 Apr 2012 09:46:02 -0500"  >Could we also add a task to notify the user when the files are about to be deleted (either in the wizard or when adding back / rebalancing)?</comment>
                    <comment id="25574" author="alkondratenko" created="Mon, 9 Apr 2012 13:52:39 -0500"  >how you want user to be notifed? We can use user-visible log message or we can have alert-like thing.</comment>
                    <comment id="25575" author="perry" created="Mon, 9 Apr 2012 13:56:18 -0500"  >I&amp;#39;d specifically like something that makes the user confirm that they understand that proceeding with whatever action will result in the deleting of files they may want to save.  A log message after the fact doesn&amp;#39;t give them the ability to recover that data.</comment>
                    <comment id="25599" author="steve" created="Mon, 9 Apr 2012 17:53:05 -0500"  >alk predicts this evening ETA</comment>
                    <comment id="25612" author="alkondratenko" created="Mon, 9 Apr 2012 21:12:13 -0500"  >&lt;a href=&quot;http://review.couchbase.org/14628&quot;&gt;http://review.couchbase.org/14628&lt;/a&gt;</comment>
                    <comment id="26071" author="thuan" created="Fri, 20 Apr 2012 17:47:39 -0500"  >Integrated in github-ns-server-2-0 #333 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ns-server-2-0/333/&quot;&gt;http://qa.hq.northscale.net/job/github-ns-server-2-0/333/&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-4564&quot; title=&quot;Don&amp;#39;t delete database files when node leaves cluster.&quot;&gt;&lt;strike&gt;MB-4564&lt;/strike&gt;&lt;/a&gt; Don&amp;#39;t delete database files when node leaves cluster. (Revision ac961c9839396f64ef6c0ef56e5f298095a0da63)&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Result = SUCCESS&lt;br/&gt;
Aliaksey Kandratsenka : &lt;br/&gt;
Files : &lt;br/&gt;
* src/ns_memcached.erl&lt;br/&gt;
* src/ns_cluster.erl&lt;br/&gt;
* src/menelaus_web_buckets.erl&lt;br/&gt;
* src/menelaus_web.erl&lt;br/&gt;
* src/ns_storage_conf.erl&lt;br/&gt;
* src/ns_rebalancer.erl&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>Mon, 30 Jan 2012 16:34:01 -0600</customfieldvalue>

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