<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 25 01:16:37 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-5938/MB-5938.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-5938] UI needs to deal with very slow docloader (alternatively, docloader is too slow)</title>
                <link>http://www.couchbase.com/issues/browse/MB-5938</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>It works fine with old samples (gamesim-sample), but recent archives (beer-sample) contains much more data and usually fail due to timeout.&lt;br/&gt;
&lt;br/&gt;
Now it takes at least 40 seconds to load documents and create views.</description>
                <environment></environment>
            <key id="18505">MB-5938</key>
            <summary>UI needs to deal with very slow docloader (alternatively, docloader is too slow)</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</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="alkondratenko">Aleksey Kondratenko</assignee>
                                <reporter username="pavelpaulau">Pavel Paulau</reporter>
                        <labels>
                        <label>2.0-beta-release-notes</label>
                    </labels>
                <created>Wed, 18 Jul 2012 13:17:44 -0500</created>
                <updated>Fri, 26 Oct 2012 18:14:36 -0500</updated>
                    <resolved>Mon, 17 Sep 2012 10:14:18 -0500</resolved>
                                            <fixVersion>recent-builds-2.0</fixVersion>
                <fixVersion>2.0-beta-2</fixVersion>
                                <component>ns_server</component>
                                <votes>1</votes>
                        <watches>3</watches>
                                                    <comments>
                    <comment id="33390" author="alkondratenko" created="Wed, 18 Jul 2012 15:08:50 -0500"  >Hm. Users are not generally prepared to wait that much. In theory there should be no problem loading thousands of docs per second. I don&amp;#39;t think beers data is mega docs.</comment>
                    <comment id="33405" author="pavelpaulau" created="Wed, 18 Jul 2012 15:30:23 -0500"  >1. before loading these docs we have to create new bucket (if it doesn&amp;#39;t exist).&lt;br/&gt;
2. every document is a separate file (for beers we have more then 6000 files in archive). and current approach to read these files is pretty weird.&lt;br/&gt;
3. we also create new ddocs/views and perform queries on new indices. &lt;br/&gt;
&lt;br/&gt;
if there is any problem with increasing timeout, I can fix point #2.</comment>
                    <comment id="33451" author="alkondratenko" created="Wed, 18 Jul 2012 16:35:38 -0500"  >Increasing timeout is simple. But waiting 40 seconds is a bit too much for users to tolerate.&lt;br/&gt;
</comment>
                    <comment id="33453" author="pavelpaulau" created="Wed, 18 Jul 2012 16:39:50 -0500"  >ok, fixing #2 doesn&amp;#39;t help sometimes.&lt;br/&gt;
&lt;br/&gt;
python client have extremely low throughput (regardless environment). and this is behind cbdocloader.&lt;br/&gt;
thus we need ~15-20 seconds to load these sample items.&lt;br/&gt;
&lt;br/&gt;
I understand that 40 seconds are too long. but nobody is going to fix/improve old sdk branch, which is only compatible with python 2.4.</comment>
                    <comment id="33485" author="alkondratenko" created="Wed, 18 Jul 2012 19:02:27 -0500"  >Trying longer timeout. That sucks. We don&amp;#39;t have good feedback for users.</comment>
                    <comment id="33556" author="dipti" created="Thu, 19 Jul 2012 14:20:36 -0500"  >Can we just make the load asynchronous and log problems? </comment>
                    <comment id="34053" author="thuan" created="Thu, 26 Jul 2012 11:08:02 -0500"  >Integrated in github-ns-server-2-0 #412 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ns-server-2-0/412/&quot;&gt;http://qa.hq.northscale.net/job/github-ns-server-2-0/412/&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-5938&quot; title=&quot;UI needs to deal with very slow docloader (alternatively, docloader is too slow)&quot;&gt;&lt;strike&gt;MB-5938&lt;/strike&gt;&lt;/a&gt;: bumped up docloader timeout to 60 seconds (Revision f6d28497ddb2270962b8ba73284da66237120be8)&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Result = SUCCESS&lt;br/&gt;
Aliaksey Artamonau : &lt;br/&gt;
Files : &lt;br/&gt;
* src/menelaus_web.erl&lt;br/&gt;
</comment>
                    <comment id="34138" author="alkondratenko" created="Fri, 27 Jul 2012 11:10:00 -0500"  >Assigning to Pavel for UI-only attempt to fix</comment>
                    <comment id="35727" author="pavel" created="Fri, 17 Aug 2012 10:32:37 -0500"  >I had tried to POST on &lt;a href=&quot;http://localhost:9001/sampleBuckets/install&quot;&gt;http://localhost:9001/sampleBuckets/install&lt;/a&gt; and after 2.8min of pending I got error 400 from server with the following response&lt;br/&gt;
{&amp;quot;error&amp;quot;:true,&amp;quot;type&amp;quot;:&amp;quot;docloader_failed&amp;quot;,&amp;quot;reason&amp;quot;:&amp;quot;There was an unexpected error.&amp;quot;}&lt;br/&gt;
&lt;br/&gt;
In this case SAMPLES_LOADING_TIMEOUT was 12000000. </comment>
                    <comment id="35728" author="alkondratenko" created="Fri, 17 Aug 2012 11:00:54 -0500"  >There&amp;#39;s blocker level bug on docloader for that</comment>
                    <comment id="35756" author="karan" created="Fri, 17 Aug 2012 13:06:31 -0500"  >Also look at &lt;br/&gt;
&lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-6274&quot;&gt;http://www.couchbase.com/issues/browse/MB-6274&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
for other docloader improvements. </comment>
                    <comment id="38509" author="alkondratenko" created="Tue, 11 Sep 2012 14:00:58 -0500"  >Not actually fixed.</comment>
                    <comment id="38510" author="alkondratenko" created="Tue, 11 Sep 2012 14:02:12 -0500"  >Sorry. Meant to assign to Pavel</comment>
                    <comment id="39165" author="pavel" created="Mon, 17 Sep 2012 10:14:18 -0500"  >&lt;a href=&quot;http://review.couchbase.org/20834&quot;&gt;http://review.couchbase.org/20834&lt;/a&gt;</comment>
                    <comment id="39172" author="alkondratenko" created="Mon, 17 Sep 2012 11:32:52 -0500"  >I&amp;#39;ve uploaded alternative commit to gerrit. Sample loading call will now return as soon as buckets are created, then data will be loaded in background and task will be reported via list of tasks (without progress report however) in right top corner.</comment>
                    <comment id="42655" author="kzeller" created="Fri, 26 Oct 2012 18:14:36 -0500"  >Sample data will now be asynchronously loaded. Loading sample data will be &lt;br/&gt;
executed as a background task then later reported in web console &lt;br/&gt;
upon completion.</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>Wed, 18 Jul 2012 15:08:50 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>4617</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                            <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                <customfieldname>Sprint Priority</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>2.0</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10052" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Sprint Status</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10027"><![CDATA[Current Sprint]]></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>