[
https://issues.apache.org/jira/browse/COUCHDB-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016494#comment-16016494
]
Joan Touzet commented on COUCHDB-3421:
--------------------------------------
HI Scott,
What do you mean by "900 messages a second?" Are you running 3 instances on the
same machine or 3 different machines? Are you load-balancing all requests
across all 3 instances, or are you making all requests against a single
instance? Have you checked iostat or similar to ensure that you're not running
into disk bandwidth limitations of your host(s)?
You can attach your files to this ticket but I'm afraid I don't have time to
look at them right now - I'm just trying to walk you through a few things off
the top of my head.
> mem3 sync shards WARNING at very low message rate, data doesn't sync
> --------------------------------------------------------------------
>
> Key: COUCHDB-3421
> URL: https://issues.apache.org/jira/browse/COUCHDB-3421
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Reporter: Scott Kaul
> Priority: Minor
>
> Sending couch messages, as low as 100 messages a second, results in couch
> falling behind on its replication with other nodes. In cluster configuration
> n, w, and r are all set to 2. While sending these messages, the following
> warning is observed:
> May 17 15:56:54 coreosnode2 docker[26520]: [warning]
> 2017-05-17T15:56:54.753466Z couchdb-3@couchdb-3.couchdb <0.309.0> --------
> mem3_sync shards/20000000-3fffffff/test.1495035040
> couchdb-2@couchdb-2.couchdb {pending_changes,151}
> Likewise after the message loader is stopped (jmeter) it takes couch a period
> of time (minutes) to complete replication before the WARNINGs are no longer
> received and couchDB CPU goes down.
> I'm happy to provide a jmx file for jmeter as well as a couple curl commands
> to delete/create the DB used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
