couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-686) Improve ordering of replication
Date Tue, 09 Mar 2010 23:00:28 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843348#action_12843348
] 

Randall Leeds commented on COUCHDB-686:
---------------------------------------

I could get behind a change that makes MAX_CONCURRENT_REQUESTS in couch_rep_reader an ini
file variable in the replication section.

I consider the current behavior a performance feature and would be -1 on any code change that
removes it.

Setting MAX_CONCURRENT_REQUESTS to 1 should give you the behavior you desire and a similarly
named configuration setting would make clear exactly what's going on to anyone who wants to
tweak it.

> Improve ordering of replication
> -------------------------------
>
>                 Key: COUCHDB-686
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-686
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 0.10.1
>            Reporter: Dirkjan Ochtman
>            Priority: Minor
>             Fix For: 0.12
>
>
> Currently, (continuous) replication almost preserves the ordering of the updates. It
would be nice if this could be fixed so that the order of outgoing updates fully corresponds
to the order inside the source database. While this may fall down in some clustering situations,
it's a great guarantee to provide in many smaller situations involving an ordered stream of
documents/updates.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message