[
https://issues.apache.org/jira/browse/COUCHDB-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016399#comment-16016399
]
Scott Kaul commented on COUCHDB-3421:
-------------------------------------
Hi Joan,
Ok, took us a day but we got couch running directly on an instance of Debian.
No docker. 8vCPU, 8GB RAM The issue is the same:
[warning] 2017-05-18T20:15:22.320498Z [email protected] <0.316.0>
-------- mem3_sync shards/a0000000-bfffffff/test.1495137986
[email protected] {pending_changes,474}
Cluster vars:
q=8, n=3, w/r=2
This 900 msgs a second results in couch using ~800% CPU.
Is there a way I can upload the jmeter file we are using along with a tiny
script that creates the test DB on a node (minor mods to both for IP address)?
Any other thoughts on what we can check?
> 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 [email protected] <0.309.0> --------
> mem3_sync shards/20000000-3fffffff/test.1495035040
> [email protected] {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)
