couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1647) Include error reason when "_replication_state":"error"
Date Tue, 03 Dec 2013 13:18:35 GMT

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

ASF subversion and git services commented on COUCHDB-1647:
----------------------------------------------------------

Commit 08cac68b26d95b90dedadbb5d162d082226ec5ca in branch refs/heads/master from [~rnewson]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=08cac68 ]

Include reason for replication failure in _replicator doc

closes COUCHDB-1647


> Include error reason when "_replication_state":"error"
> ------------------------------------------------------
>
>                 Key: COUCHDB-1647
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1647
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Nathan Vander Wilt
>
> Right now when a replication gets into an error state, one must go into the logs (if
they go back far enough) to figure out what happened. Can this be recorded on the replication
doc alongside the error state?
> e.g. I'd like:
> {
>    "_id": "my_replication",
> …
>    "_replication_state": "error",
>    "_replication_state_time": "2013-01-14T21:58:29+00:00",
>    "_replication_state_reason": "HERE IS WHAT WENT WRONG."
> }



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message