<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 21:14:21 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-7170/MB-7170.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-7170] sample loader fails if there are multiple nodes in the cluster and bucket creation time takes more than few seconds</title>
                <link>http://www.couchbase.com/issues/browse/MB-7170</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>create bucket api returns immediately but that does not mean the bucket and db files are ready on all nodes.&lt;br/&gt;
&lt;br/&gt;
sample loader only waits a few seconds until that happens.&lt;br/&gt;
it needs to wait for the bucket to be ready on all nodes either via checking with memcached or ns-server&lt;br/&gt;
&lt;br/&gt;
Loading sample bucket beer-sample failed: {failed_to_load_samples_with_status,&lt;br/&gt;
1}&lt;br/&gt;
&lt;br/&gt;
if you have a cluster with 2 buckets and 3 nodes and then click on sample loader you will see this behavior</description>
                <environment></environment>
            <key id="20709">MB-7170</key>
            <summary>sample loader fails if there are multiple nodes in the cluster and bucket creation time takes more than few seconds</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="abhinav">Abhinav Dangeti</assignee>
                                <reporter username="farshid">Farshid Ghods</reporter>
                        <labels>
                        <label>2.0-release-notes</label>
                    </labels>
                <created>Tue, 13 Nov 2012 08:49:34 -0600</created>
                <updated>Tue, 9 Apr 2013 19:54:31 -0500</updated>
                    <resolved>Mon, 1 Apr 2013 20:39:40 -0500</resolved>
                                            <fixVersion>2.0.2</fixVersion>
                <fixVersion>2.1</fixVersion>
                                <component>tools</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="43900" author="farshid" created="Tue, 13 Nov 2012 11:18:06 -0600"  >in QE tests this code verifies that bucket is ready to accept mutations before proceeding&lt;br/&gt;
&lt;br/&gt;
&lt;a href=&quot;https://github.com/couchbase/testrunner/blob/master/lib/membase/helper/bucket_helper.py#L208&quot;&gt;https://github.com/couchbase/testrunner/blob/master/lib/membase/helper/bucket_helper.py#L208&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
im sure ns-server has a much better way of detecting that.</comment>
                    <comment id="44790" author="steve" created="Mon, 26 Nov 2012 14:38:27 -0600"  >to 2.0.2 per bug-scrub</comment>
                    <comment id="53958" author="maria" created="Mon, 1 Apr 2013 20:31:31 -0500"  >per bug scrub: PM requesting 1 last time for QE to repro. If not reproducible, close this bug. Thanks.</comment>
                    <comment id="53961" author="abhinav" created="Mon, 1 Apr 2013 20:39:35 -0500"  >Not reproducible on 2.0.2-749-rel, tested on Centos: 3 node cluster, with 3 pre-existing buckets.&lt;br/&gt;
Created both gamesim-sample and beer-sample alright.</comment>
                    <comment id="54685" author="maria" created="Tue, 9 Apr 2013 19:54:31 -0500"  >not reproducible.</comment>
                </comments>
                    <attachments>
                    <attachment id="15794" name="ns-diag-20121113090931.txt.zip" size="10409876" author="farshid" created="Tue, 13 Nov 2012 11:18:06 -0600" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Mon, 26 Nov 2012 14:38:27 -0600</customfieldvalue>

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