couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1648) Include checkpoint/progress information in _replicator docs
Date Tue, 15 Jan 2013 05:34:13 GMT

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

Alexander Shorin commented on COUCHDB-1648:
-------------------------------------------

Probably, it's reasonable to include such information if replication have failed (e.g. point
of failure) unless this will require often replication document updates which makes replicator
database size grow extremely fast. I'm imagine with fear over 9K useless updates for single
replicator task for my biggest database...
                
> Include checkpoint/progress information in _replicator docs
> -----------------------------------------------------------
>
>                 Key: COUCHDB-1648
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1648
>             Project: CouchDB
>          Issue Type: Wish
>          Components: Replication
>            Reporter: Nathan Vander Wilt
>
> Similar to COUCHDB-1647 but arguably a bit less important, it'd be great to have progress
information alongside the replication_state/replication_state_time fields in triggered replicator
documents.
> In normal CouchDB the advantages would be having all the info in one place, and tracking
replication states using the _changes field rather than constantly polling active tasks. Would
also be great on the BigCouch side which doesn't seem to include _replicator docs in its _active_tasks
list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message