[
https://issues.apache.org/jira/browse/COUCHDB-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016782#comment-16016782
]
Joan Touzet commented on COUCHDB-3421:
--------------------------------------
It's worth noting that the cluster can handle this much load but it makes sense
to spread it across all 3 machines. The specific performance limit for any
given node is a combination of many, many factors, and I can't easily give you
a one-size-fits-all answer as to how much it should be able to handle.
At this point I'm unconvinced you're running into an actual bug. I'll keep this
ticket open for a bit longer, but if you're looking for advice on setting up
and configuring CouchDB at scale, there are multiple professional services
organizations that can help you with that - I'm just one volunteer with many
hats to wear.
> 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)
