Uploaded image for project: 'CouchDB'
  1. CouchDB
  2. COUCHDB-1647

Include error reason when "_replication_state":"error"

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.6.0
    • Component/s: Replication
    • Labels:
      None

      Description

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

        Issue Links

          Activity

          Hide
          jira-bot ASF subversion and git services added a comment -

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

          Include reason for replication failure in _replicator doc

          closes COUCHDB-1647

          Show
          jira-bot ASF subversion and git services added a comment - Commit 08cac68b26d95b90dedadbb5d162d082226ec5ca in branch refs/heads/master from Robert Newson [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=08cac68 ] Include reason for replication failure in _replicator doc closes COUCHDB-1647
          Hide
          rnewson Robert Newson added a comment -

          _replication_state_reason will be populated on transition to error state.

          Show
          rnewson Robert Newson added a comment - _replication_state_reason will be populated on transition to error state.

            People

            • Assignee:
              Unassigned
              Reporter:
              natevw Nathan Vander Wilt
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development