<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed Jun 19 07:48:41 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-4006/MB-4006.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-4006] mb_mnesia,ensure_schema timeout when restarting ns_server</title>
                <link>http://www.couchbase.com/issues/browse/MB-4006</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>users are run into this issue too often which i suspect has sth to do with the uptime or maybe an unclean shutdown of the server can result in this behavior.&lt;br/&gt;
&lt;br/&gt;
asking customers to delete their statistics is not a very pleasent thing to do&lt;br/&gt;
&lt;br/&gt;
</description>
                <environment>1.7 GA</environment>
            <key id="14403">MB-4006</key>
            <summary>mb_mnesia,ensure_schema timeout when restarting ns_server</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="2" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/critical.png">Critical</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="4">Incomplete</resolution>
                    <security id="10011">Public</security>
                        <assignee username="alkondratenko">Aleksey Kondratenko</assignee>
                                <reporter username="farshid">Farshid Ghods</reporter>
                        <labels>
                        <label>1.7.0-release-notes</label>
                        <label>1.8.0-release-notes</label>
                    </labels>
                <created>Wed, 22 Jun 2011 11:23:45 -0500</created>
                <updated>Tue, 9 Apr 2013 12:54:13 -0500</updated>
                    <resolved>Mon, 8 Apr 2013 18:59:01 -0500</resolved>
                            <version>1.7 GA</version>
                <version>1.7.2</version>
                                                <component>ns_server</component>
                                <votes>1</votes>
                        <watches>4</watches>
                                                    <comments>
                    <comment id="21230" author="farshid" created="Wed, 22 Jun 2011 11:37:06 -0500"  >When a process is killed or dies, mnesia files might be left in a poor state that prevents restart.</comment>
                    <comment id="21264" author="farshid" created="Thu, 30 Jun 2011 10:41:14 -0500"  >the workaround is to remove all files under /opt/membase/var/lib/membase/mnesia/*.*</comment>
                    <comment id="21275" author="alkondratenko" created="Tue, 5 Jul 2011 14:03:00 -0500"  >fix merged</comment>
                    <comment id="25890" author="farshid" created="Tue, 17 Apr 2012 01:19:07 -0500"  >reported by a user on 1.7.2 &lt;br/&gt;
diags here : &lt;a href=&quot;http://www63.zippyshare.com/v/19241756/file.html&quot;&gt;http://www63.zippyshare.com/v/19241756/file.html&lt;/a&gt; </comment>
                    <comment id="26549" author="alkondratenko" created="Wed, 2 May 2012 13:39:15 -0500"  >thanks for raising this again.&lt;br/&gt;
&lt;br/&gt;
Looks like our workaround is not working all the time. For now manual workaround of deleting mnesia files and starting ns_server again will work.&lt;br/&gt;
&lt;br/&gt;
For future we&amp;#39;ll get rid of mnesia completely.&lt;br/&gt;
</comment>
                    <comment id="26552" author="alkondratenko" created="Wed, 2 May 2012 13:56:04 -0500"  >Dipti, maybe I&amp;#39;m missing something and stats-in-mnesia is not &amp;quot;unfixable crap&amp;quot;. But my plan since before 1.7.0 was to replace saving stats in mnesia with much simpler periodic snapshotting into plain file. Because stats are not really precious thing.&lt;br/&gt;
&lt;br/&gt;
I estimate this work to be around 1-2 days including thorough testing.&lt;br/&gt;
&lt;br/&gt;
We also had some plans for storing stats in couch, but given KISS principle I think my simplified approach is what we need.&lt;br/&gt;
&lt;br/&gt;
Please, decide when we want this work to be done.</comment>
                    <comment id="26569" author="alkondratenko" created="Wed, 2 May 2012 17:33:44 -0500"  >Let me explain &amp;quot;not really precious thing&amp;quot; better. Apparently it&amp;#39;s too easily to misunderstand my original phrase as &amp;quot;we shouldn&amp;#39;t save stats at all&amp;quot;.&lt;br/&gt;
&lt;br/&gt;
Mnesia does it&amp;#39;s own journalling and crash recovery and durable commits and stuff like that. Or supposedly does.&lt;br/&gt;
&lt;br/&gt;
My point was we don&amp;#39;t need _that_ level of durability. That means that instead of trying to commit supposedly durable transaction via mnesia after each stats sample we&amp;#39;ll accumulate changes and save them once or twice per minute. Saving itself (because it&amp;#39;s not much data) can be made durable and cheap.&lt;br/&gt;
&lt;br/&gt;
</comment>
                    <comment id="26582" author="dc" created="Wed, 2 May 2012 19:16:36 -0500"  >Attaching the relevant logs.</comment>
                    <comment id="54556" author="alkondratenko" created="Mon, 8 Apr 2013 18:59:01 -0500"  >Invalidated by removal of mnesia</comment>
                    <comment id="54600" author="dipti" created="Mon, 8 Apr 2013 21:40:44 -0500"  >have you already removed mnesia? &lt;br/&gt;
&lt;br/&gt;
If so is there any impact in the upgrade process ? </comment>
                    <comment id="54655" author="alkondratenko" created="Tue, 9 Apr 2013 12:54:13 -0500"  >The code was actually ready for 2.0.1 but sadly too late. So 2.0.2 got it early.&lt;br/&gt;
&lt;br/&gt;
Impact on upgrade process is simple. People will lose their stats archive. I.e. we don&amp;#39;t bother converting stats from mnesia to new format. But note that rolling upgrade already causes them to lose historical stats.</comment>
                </comments>
                    <attachments>
                    <attachment id="12985" name="log.rar" size="3605714" author="dc" created="Wed, 2 May 2012 19:16:36 -0500" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Tue, 5 Jul 2011 14:03:00 -0500</customfieldvalue>

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