You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Randall Leeds (JIRA)" <ji...@apache.org> on 2010/05/18 01:16:44 UTC

[jira] Commented: (COUCHDB-686) Improve ordering of replication

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

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

I think this task can be closed.
In the 0.11 we have the [replicator] options section. Setting max_http_sessions to 1 should accomplish the desired result, I think.
It's been a while since I thought about this ticket though, so maybe I'm missing something.

> 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.