<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 18 23:07:54 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-7286/MB-7286.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-7286] UI logs showing multiple errors, (XDCR bi and uni, at the start of a rebalance-in operation): Server error during processing: [&quot;web request failed&quot; ...</title>
                <link>http://www.couchbase.com/issues/browse/MB-7286</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>+ 5 nodes rebalance in on each cluster&lt;br/&gt;
Cluster setup: c1:c2::10:10 &lt;br/&gt;
biXDCR_bucket: c1 &amp;lt;---&amp;gt; c2 &lt;br/&gt;
uniXDCR_src: c1 ---&amp;gt; c2 :uniXDCR_dest &lt;br/&gt;
Front end loads on c1 and c2 for biXDCR_bucket, and on c1 for uniXDCR_src. &lt;br/&gt;
c1: &lt;a href=&quot;http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/&quot;&gt;http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/&lt;/a&gt; &lt;br/&gt;
c2: &lt;a href=&quot;http://ec2-175-41-186-167.ap-southeast-1.compute.amazonaws.com:8091/&quot;&gt;http://ec2-175-41-186-167.ap-southeast-1.compute.amazonaws.com:8091/&lt;/a&gt; &lt;br/&gt;
&lt;br/&gt;
UI reports whole bunch of these errors at the start of rebalancing operation and with the front end loads:&lt;br/&gt;
Server error during processing: [&amp;quot;web request failed&amp;quot;,&lt;br/&gt;
{path,&amp;quot;/pools/default&amp;quot;},&lt;br/&gt;
{type,exit},&lt;br/&gt;
{what,&lt;br/&gt;
{timeout,&lt;br/&gt;
{gen_server,call,&lt;br/&gt;
[ns_doctor,get_tasks_version]}}},&lt;br/&gt;
{trace,&lt;br/&gt;
[{gen_server,call,2},&lt;br/&gt;
{menelaus_web,build_pool_info,4},&lt;br/&gt;
{menelaus_web,handle_pool_info_wait,5},&lt;br/&gt;
{menelaus_web,loop,3},&lt;br/&gt;
{mochiweb_http,headers,5},&lt;br/&gt;
{proc_lib,init_p_do_apply,3}]}] (repeated 1 times)&lt;br/&gt;
&lt;br/&gt;
Will attach grabbed diags from the particular server in a bit.&lt;br/&gt;
</description>
                <environment>- 5:5 bidirectional XDCR &lt;br/&gt;
- ec2 nodes with 15G RAM &lt;br/&gt;
- 12.04 Ubuntu LTS &lt;br/&gt;
- 400G disk space on each node &lt;br/&gt;
- &lt;a href=&quot;http://builds.hq.northscale.net/latestbuilds/couchbase-server-enterprise_x86_64_2.0.0-1967-rel.deb.manifest.xml&quot;&gt;http://builds.hq.northscale.net/latestbuilds/couchbase-server-enterprise_x86_64_2.0.0-1967-rel.deb.manifest.xml&lt;/a&gt;</environment>
            <key id="20997">MB-7286</key>
            <summary>UI logs showing multiple errors, (XDCR bi and uni, at the start of a rebalance-in operation): Server error during processing: [&quot;web request failed&quot; ...</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="1" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="Aliaksey Artamonau">Aliaksey Artamonau</assignee>
                                <reporter username="abhinav">Abhinav Dangeti</reporter>
                        <labels>
                        <label>2.0-release-notes</label>
                    </labels>
                <created>Wed, 28 Nov 2012 21:00:35 -0600</created>
                <updated>Mon, 18 Feb 2013 11:31:48 -0600</updated>
                                    <version>2.0</version>
                                <fixVersion>2.1</fixVersion>
                                <component>ns_server</component>
                <component>UI</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="44983" author="abhinav" created="Wed, 28 Nov 2012 21:38:58 -0600"  >UI reports that this error seems to be on server node: &lt;a href=&apos;mailto:ns_1@ec2-177-71-230-72.sa-east-1.compute.amazonaws.com&apos;&gt;ns_1@ec2-177-71-230-72.sa-east-1.compute.amazonaws.com&lt;/a&gt;&lt;br/&gt;
Grabbed diags: &lt;a href=&quot;https://s3.amazonaws.com/bugdb/MB-7286/ec2-177-71-230-72.sa-east-1.compute.amazonaws.com-8091-diag.txt.gz&quot;&gt;https://s3.amazonaws.com/bugdb/MB-7286/ec2-177-71-230-72.sa-east-1.compute.amazonaws.com-8091-diag.txt.gz&lt;/a&gt;</comment>
                    <comment id="45013" author="steve" created="Thu, 29 Nov 2012 13:17:20 -0600"  >from bug-scrub.&lt;br/&gt;
&lt;br/&gt;
ketaki: errors seem to go away after 10 minutes, but cluster is unaccessible?</comment>
                    <comment id="45014" author="steve" created="Thu, 29 Nov 2012 13:18:22 -0600"  >per-bug-scrub, moved to 2.0.1</comment>
                    <comment id="45499" author="kzeller" created="Wed, 5 Dec 2012 14:23:10 -0600"  >Added to RN:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;During a rebalance operation for clusters undergoing uni- and bi-directional replication &lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;via XDCR, the following server errors may appear, which are currently under &lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;investigation:</comment>
                    <comment id="45515" author="junyi" created="Wed, 5 Dec 2012 15:29:02 -0600"  >Seems to me these errors usually mean the system is busy working on something which is pretty heavy (like rebalance, etc), and is unable to respond to UI request timely.  Waiting for triage from ns_server team.</comment>
                    <comment id="45705" author="farshid" created="Mon, 10 Dec 2012 11:30:19 -0600"  >deferring to 2.1 per bug scrub meeting ( Dipti &amp;amp; Farshid -December 7th )</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>Thu, 29 Nov 2012 13:17:20 -0600</customfieldvalue>

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