[
https://issues.apache.org/jira/browse/COUCHDB-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson resolved COUCHDB-1647.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
_replication_state_reason will be populated on transition to error state.
> 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
> Fix For: 1.6.0
>
>
> 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)
