<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 25 19:09:38 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-6662/MB-6662.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-6662] XDC: worse performance with expired items</title>
                <link>http://www.couchbase.com/issues/browse/MB-6662</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>Unidir symptoms (expiration ratio: 3%, expiration time: 5 minutes):&lt;br/&gt;
-- extremely high XDC ops/sec and XDC gets/sec rate on destination side. At the same time actual replication rate (new items/sec) is very low.&lt;br/&gt;
-- XDC queue grows all the time on source side (unlike case w/o expired items)</description>
                <environment>VMs, CentOS 6.2, 4-to-4 nodes, build 1723</environment>
            <key id="19768">MB-6662</key>
            <summary>XDC: worse performance with expired items</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="chiyoung">Chiyoung Seo</assignee>
                                <reporter username="pavelpaulau">Pavel Paulau</reporter>
                        <labels>
                        <label>pblock</label>
                    </labels>
                <created>Fri, 14 Sep 2012 11:17:25 -0500</created>
                <updated>Wed, 19 Sep 2012 21:01:14 -0500</updated>
                    <resolved>Mon, 17 Sep 2012 20:17:39 -0500</resolved>
                                                            <component>cross-datacenter-replication</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="38902" author="pavelpaulau" created="Fri, 14 Sep 2012 11:19:12 -0500"  >Ketaki,&lt;br/&gt;
Please update/close your bug and assign this issue to Junyi.&lt;br/&gt;
&lt;br/&gt;
&lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-6563&quot;&gt;http://www.couchbase.com/issues/browse/MB-6563&lt;/a&gt;</comment>
                    <comment id="38928" author="pavelpaulau" created="Fri, 14 Sep 2012 13:55:59 -0500"  >jic: reports.</comment>
                    <comment id="39039" author="junyi" created="Fri, 14 Sep 2012 16:56:43 -0500"  >Known issue. Duplicate of &lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-6563&quot; title=&quot;Replication ops/sec drops to 0, on stop/start load from source cluster. [Load with only creates looks okay, load with expired items--&amp;gt; replication rate drops very low.]&quot;&gt;&lt;strike&gt;MB-6563&lt;/strike&gt;&lt;/a&gt;. </comment>
                    <comment id="39041" author="ketaki" created="Fri, 14 Sep 2012 17:03:39 -0500"  >Closed &lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-6563&quot; title=&quot;Replication ops/sec drops to 0, on stop/start load from source cluster. [Load with only creates looks okay, load with expired items--&amp;gt; replication rate drops very low.]&quot;&gt;&lt;strike&gt;MB-6563&lt;/strike&gt;&lt;/a&gt;, using this bug to track expired items.</comment>
                    <comment id="39056" author="pavelpaulau" created="Fri, 14 Sep 2012 17:47:06 -0500"  >Tried build 1723 w/o expired items and everything looks fine (at least as it was before).</comment>
                    <comment id="39096" author="junyi" created="Fri, 14 Sep 2012 21:48:17 -0500"  >OK, Pavel reproduced the issue. Now it looks like it is a bug in ep_engine incorrectly account the getMeta ops.&lt;br/&gt;
&lt;br/&gt;
I deleted replication on the source cluster at 19:29PM and XDCR activity is stopped.  Look at logs at 10.2.2.190, there is no capi_replication trace after 19:29PM. However, on the UI it keeps showing very high rate of getMeta in XDC section.  &lt;br/&gt;
&lt;br/&gt;
Please look at screen shot:  Junyi-Pavel-test Screen Shot 2012-09-14 at 7.39.21 PM.png from one of destination 10.2.2.190&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
By cbstats, you see the get_meta ops keep increasing (while del/set ops have no change) after I stopped the XDCR completely.&lt;br/&gt;
&lt;br/&gt;
Junyis-MacBook-Pro:management junyi$ cbstats 10.2.2.190:11211 all | grep meta&lt;br/&gt;
&amp;nbsp;ep_num_ops_del_meta:                34329&lt;br/&gt;
&amp;nbsp;ep_num_ops_get_meta:                41910986&lt;br/&gt;
&amp;nbsp;ep_num_ops_set_meta:                14257849&lt;br/&gt;
Junyis-MacBook-Pro:management junyi$ cbstats 10.2.2.190:11211 all | grep meta&lt;br/&gt;
&amp;nbsp;ep_num_ops_del_meta:                34329&lt;br/&gt;
&amp;nbsp;ep_num_ops_get_meta:                44140162&lt;br/&gt;
&amp;nbsp;ep_num_ops_set_meta:                14257849&lt;br/&gt;
Junyis-MacBook-Pro:management junyi$ cbstats 10.2.2.190:11211 all | grep meta&lt;br/&gt;
&amp;nbsp;ep_num_ops_del_meta:                34329&lt;br/&gt;
&amp;nbsp;ep_num_ops_get_meta:                44226426&lt;br/&gt;
&amp;nbsp;ep_num_ops_set_meta:                14257849&lt;br/&gt;
Junyis-MacBook-Pro:management junyi$ cbstats 10.2.2.190:11211 all | grep meta&lt;br/&gt;
&amp;nbsp;ep_num_ops_del_meta:                34329&lt;br/&gt;
&amp;nbsp;ep_num_ops_get_meta:                44254887&lt;br/&gt;
&amp;nbsp;ep_num_ops_set_meta:                14257849&lt;br/&gt;
Junyis-MacBook-Pro:management junyi$ cbstats 10.2.2.190:11211 all | grep meta&lt;br/&gt;
&amp;nbsp;ep_num_ops_del_meta:                34329&lt;br/&gt;
&amp;nbsp;ep_num_ops_get_meta:                44273589&lt;br/&gt;
&amp;nbsp;ep_num_ops_set_meta:                14257849&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Since no activity after 19:29PM,  these getMeta should come from CAPI/XDCR,  looks more likely  the ep_engine incorrectly account the getMeta operations. It is a blocker IMHO, and hand over to Chiyoung for investigation.&lt;br/&gt;
&lt;br/&gt;
Thanks.&lt;br/&gt;
&lt;br/&gt;
</comment>
                    <comment id="39223" author="chiyoung" created="Mon, 17 Sep 2012 20:17:39 -0500"  >&lt;a href=&quot;http://review.couchbase.org/#/c/20927/1&quot;&gt;http://review.couchbase.org/#/c/20927/1&lt;/a&gt;</comment>
                    <comment id="39329" author="pavelpaulau" created="Wed, 19 Sep 2012 16:34:06 -0500"  >Verified.</comment>
                    <comment id="39376" author="thuan" created="Wed, 19 Sep 2012 21:01:14 -0500"  >Integrated in github-ep-engine-2-0 #431 (See [&lt;a href=&quot;http://qa.hq.northscale.net/job/github-ep-engine-2-0/431/&quot;&gt;http://qa.hq.northscale.net/job/github-ep-engine-2-0/431/&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-6662&quot; title=&quot;XDC: worse performance with expired items&quot;&gt;&lt;strike&gt;MB-6662&lt;/strike&gt;&lt;/a&gt; Ignore the item&amp;#39;s expiration time for SET_WITH_META (Revision 5a9b619ae5c9c65c3a1e2902d57f60d0e4915c59)&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Result = SUCCESS&lt;br/&gt;
Chiyoung Seo : &lt;br/&gt;
Files : &lt;br/&gt;
* src/stored-value.hh&lt;br/&gt;
</comment>
                </comments>
                    <attachments>
                    <attachment id="15055" name="debug.tar.gz" size="493081" author="pavelpaulau" created="Fri, 14 Sep 2012 21:43:18 -0500" />
                    <attachment id="15053" name="Junyi-dest Screen Shot 2012-09-14 at 6.26.39 PM.png" size="209341" author="junyi" created="Fri, 14 Sep 2012 20:36:13 -0500" />
                    <attachment id="15056" name="Junyi-Pavel-test Screen Shot 2012-09-14 at 7.39.21 PM.png" size="180429" author="junyi" created="Fri, 14 Sep 2012 21:48:43 -0500" />
                    <attachment id="15054" name="JUNYI-Source Screen Shot 2012-09-14 at 6.35.10 PM.png" size="150525" author="junyi" created="Fri, 14 Sep 2012 20:36:13 -0500" />
                    <attachment id="15042" name="xperf-mixed-1-bi.loop_2.0.0-1723-rel-enterprise_2.0.0-1723-rel-enterprise_DEST_Sep-14-2012_11-45-45.pdf" size="755965" author="pavelpaulau" created="Fri, 14 Sep 2012 13:55:59 -0500" />
                    <attachment id="15043" name="xperf-mixed-1-bi.loop_2.0.0-1723-rel-enterprise_2.0.0-1723-rel-enterprise_SOURCE_Sep-14-2012_11-42-14.pdf" size="680133" author="pavelpaulau" created="Fri, 14 Sep 2012 13:55:59 -0500" />
                    <attachment id="15040" name="xperf-mixed-1-uni.loop_2.0.0-1723-rel-enterprise_2.0.0-1723-rel-enterprise_SOURCE_Sep-13-2012_20-27-31.pdf" size="1326013" author="pavelpaulau" created="Fri, 14 Sep 2012 13:55:59 -0500" />
                    <attachment id="15041" name="xperf-read-1-uni.loop_2.0.0-1723-rel-enterprise_2.0.0-1723-rel-enterprise_DEST_Sep-13-2012_20-32-02.pdf" size="1123077" author="pavelpaulau" created="Fri, 14 Sep 2012 13:55:59 -0500" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Fri, 14 Sep 2012 16:56:43 -0500</customfieldvalue>

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