couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Alfke (JIRA)" <>
Subject [jira] [Created] (COUCHDB-1570) Replicator writes corrupt remote checkpoint document on error; breaks revision forever
Date Sun, 21 Oct 2012 19:54:12 GMT
Jens Alfke created COUCHDB-1570:

             Summary: Replicator writes corrupt remote checkpoint document on error; breaks
revision forever
                 Key: COUCHDB-1570
             Project: CouchDB
          Issue Type: Bug
          Components: Replication
    Affects Versions: 1.2
         Environment: Mac OS X 10.8.2
            Reporter: Jens Alfke
            Priority: Minor

If a 'push' replication receives error responses from the remote server while PUTting documents,
it may write a corrupt checkpoint document to the remote server -- its _revisions._ids property
is null. Any subsequent attempt to push to that server will cause the replicator to abort
with an error when reading that replication document, since it requires _revisions.ids to
be an array.

The only workaround for this, short of deleting the remote database entirely, is to (a) identify
the URL of the remote checkpoint document, and (b) delete it from the remote server. Otherwise
you will never be able to push to that database again.

Here's a failed replication attempt:

$ curl -X POST --user snej :5984/_replicate --header Content-Type:application/json --data
{"error":"doc_validation","reason":"_revisions.ids isn't a array."}

Here's the contents of the remote checkpoint document, once I identified its ID:

$ curl :4984/demo-shopping-attachments/_local/5b913befe682d7bd1fbc24b1ce31cbc5
21 Oct 2012 19:40:04 GMT","missing_checked":17,"missing_found":2,"recorded_seq":207,"session_id":"9a24dc37885b5b4e507ea90702b2fecf","start_last_seq":0,"start_time":"Sun,
21 Oct 2012 19:40:04 GMT"}],"replication_id_version":2,"session_id":"9a24dc37885b5b4e507ea90702b2fecf","source_last_seq":207}

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:

View raw message