<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed Jun 19 18:31:42 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-6643/MB-6643.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-6643] Very slow replication rate( less than 100 on average) with 2 unidirectional replications between 2 clusters.</title>
                <link>http://www.couchbase.com/issues/browse/MB-6643</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>- Setup two 3 node clusters.&lt;br/&gt;
- Load 3M items on bucket1, cluster1 and 3M on bucket2, cluster2 [No expires on any load]&lt;br/&gt;
Example&lt;br/&gt;
-nohup lib/perf_engines/mcsoda.py localhost:23201 vbuckets=1024 doc-gen=0 doc-cache=0 ratio-creates=1 ratio-sets=1 min-value-size=256 max-items=1000000 exit-after-creates=1 prefix=a_one&lt;br/&gt;
-nohup lib/perf_engines/mcsoda.py localhost:23202 vbuckets=1024 doc-gen=0 doc-cache=0 ratio-creates=1 ratio-sets=1 min-value-size=256 max-items=1000000 exit-after-creates=1 prefix=a_two&lt;br/&gt;
-nohup lib/perf_engines/mcsoda.py localhost:23203 vbuckets=1024 doc-gen=0 doc-cache=0 ratio-creates=1 ratio-sets=1 min-value-size=256 max-items=1000000 exit-after-creates=1 prefix=a_three&lt;br/&gt;
&lt;br/&gt;
Start unidirectional from cluster1 bucket1 to cluster2 bucket1&lt;br/&gt;
Start unidirectional from cluster2 bucket2 to cluster1 bucket2&lt;br/&gt;
&lt;br/&gt;
Keep load running on cluster1 -new load with deletes/expires&lt;br/&gt;
lib/perf_engines/mcsoda.py localhost:23203 vbuckets=1024 doc-gen=0 doc-cache=0 ratio-creates=1 ratio-sets=1 ratio-deletes=0.02 ratio-expirations=0.05 expirations=1200 min-value-size=256 max-items=1000000 exit-after-creates=1 prefix=a_four&amp;amp;&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Observing very slow replication rate on cluster1 and close to 100 percent CPU used.&lt;br/&gt;
&lt;br/&gt;
Replication rate on cluster 1 is between 10 - 115&lt;br/&gt;
Replication rate on cluster2 - is between 1-2k&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Adding screenshots from cluster1.&lt;br/&gt;
&lt;br/&gt;
</description>
                <environment>2.0-1717&lt;br/&gt;
1024 vbuckets&lt;br/&gt;
&lt;br/&gt;
2 unidirectional replications on 2 clusters.&lt;br/&gt;
&lt;br/&gt;
Centos&lt;br/&gt;
&lt;br/&gt;
6G, 4 core VMs</environment>
            <key id="19740">MB-6643</key>
            <summary>Very slow replication rate( less than 100 on average) with 2 unidirectional replications between 2 clusters.</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="6" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/closed.png">Closed</status>
                    <resolution id="3">Duplicate</resolution>
                    <security id="10011">Public</security>
                        <assignee username="junyi">Junyi Xie</assignee>
                                <reporter username="ketaki">Ketaki Gangal</reporter>
                        <labels>
                        <label>2.0-beta-release-notes</label>
                        <label>pblock</label>
                    </labels>
                <created>Thu, 13 Sep 2012 12:21:35 -0500</created>
                <updated>Wed, 26 Sep 2012 16:46:52 -0500</updated>
                    <resolved>Wed, 19 Sep 2012 15:21:13 -0500</resolved>
                            <version>2.0-beta-2</version>
                                <fixVersion>2.0-beta-2</fixVersion>
                                <component>cross-datacenter-replication</component>
                                <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="38756" author="ketaki" created="Thu, 13 Sep 2012 13:55:13 -0500"  >Over a period of time, xdc gets is much higher but xdc sets is low.&lt;br/&gt;
&lt;br/&gt;
Seeing 9K/sec Xdc ops and gets 9K/sec and creates &amp;lt;100 per sec on the cluster.</comment>
                    <comment id="38764" author="junyi" created="Thu, 13 Sep 2012 14:40:26 -0500"  >Unable to tell a lot from the screen shot.  Please post more information about two clusters, e.g, the complete screenshot with XDC sections (Replication and Destination).&lt;br/&gt;
&lt;br/&gt;
Also, you load data from your local machine from the commands above. Can you please load the data from another machine in your test?</comment>
                    <comment id="38769" author="ketaki" created="Thu, 13 Sep 2012 15:29:09 -0500"  >The clusters are still running here&lt;br/&gt;
&lt;br/&gt;
&lt;a href=&quot;http://10.3.121.32:8091/index.html#sec=analytics&amp;statsBucket=%2Fpools%2Fdefault%2Fbuckets%2Fbucket1%3Fbucket_uuid%3Db0a2f01b5f787f2f85f7978a42d99a6b&amp;zoom=zoom_minute&amp;graph=ep_ops_create&quot;&gt;http://10.3.121.32:8091/index.html#sec=analytics&amp;amp;statsBucket=%2Fpools%2Fdefault%2Fbuckets%2Fbucket1%3Fbucket_uuid%3Db0a2f01b5f787f2f85f7978a42d99a6b&amp;amp;zoom=zoom_minute&amp;amp;graph=ep_ops_create&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
&lt;a href=&quot;http://10.3.121.38:8091/index.html#sec=analytics&amp;statsBucket=%2Fpools%2Fdefault%2Fbuckets%2Fbucket1%3Fbucket_uuid%3Db0a2f01b5f787f2f85f7978a42d99a6b&amp;zoom=zoom_minute&amp;graph=ep_ops_create&quot;&gt;http://10.3.121.38:8091/index.html#sec=analytics&amp;amp;statsBucket=%2Fpools%2Fdefault%2Fbuckets%2Fbucket1%3Fbucket_uuid%3Db0a2f01b5f787f2f85f7978a42d99a6b&amp;amp;zoom=zoom_minute&amp;amp;graph=ep_ops_create&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
Loading commands are put up on the bug description above. I am not loading data from my local machine, it is from different clients.&lt;br/&gt;
&lt;br/&gt;
The screenshot was from one of the relevant clusters with XDC ops/sec and XDC create/sec rate. I will add the other one as well.&lt;br/&gt;
&lt;br/&gt;
</comment>
                    <comment id="39306" author="junyi" created="Wed, 19 Sep 2012 15:21:00 -0500"  >This sounds the same issue as &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; because you have expired items in workload, and you see extremely high getMeta ops but very low setWithMeta/DeleteWithMeta. &lt;br/&gt;
&lt;br/&gt;
&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; has been fixed by recent commits. </comment>
                    <comment id="39307" author="junyi" created="Wed, 19 Sep 2012 15:21:13 -0500"  >&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;</comment>
                </comments>
                    <attachments>
                    <attachment id="15011" name="Screen Shot 2012-09-13 at 10.14.38 AM.png" size="96812" author="ketaki" created="Thu, 13 Sep 2012 12:21:35 -0500" />
                    <attachment id="15012" name="Screen Shot 2012-09-13 at 10.14.47 AM.png" size="19038" author="ketaki" created="Thu, 13 Sep 2012 12:21:35 -0500" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Thu, 13 Sep 2012 14:40:26 -0500</customfieldvalue>

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