[ https://issues.apache.org/jira/browse/COUCHDB-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868454#action_12868454 ]
Damien Katz commented on COUCHDB-763: ------------------------------------- This looks to be the same issue to what Simon Eisenmann encountered. I believe the problem was 2 databases servers running at the same time for a short time during an internal auto-restart. This problem has been fixed in trunk. > duplicate and or missing revisions in changes feed > -------------------------------------------------- > > Key: COUCHDB-763 > URL: https://issues.apache.org/jira/browse/COUCHDB-763 > Project: CouchDB > Issue Type: Bug > Components: Database Core > Affects Versions: 0.10.1 > Reporter: Randall Leeds > Priority: Critical > > I have no idea if this is unique to 0.10.1 or if it shows up on 0.11/trunk > since I have no clue how to repro. > If we can identify why this happens we should work to be very sure it's fixed. > I see something like the following in my changes feed (taken from consecutive > lines of an actually changes feed): > {"seq":36527,"id":"anonymized_docid","changes":[{"rev":"2186-967dbcd9d960b77955fcf6048fb219cc"}]}, > {"seq":36530,"id":"anonymized_docid","changes":[{"rev":"2188-ae8481b29fd3a42d5190aba7c13a522b"}]}, > I was under the impression that _changes only showed the newest revision for > any document. > Furthermore, the first of these two is actually missing. Querying the > document with ?revs_info=true shows it as such and this is confirmed by > trying to query for ?rev=2186-967dbcd9d960b77955fcf6048fb219cc > 1) Missing revisions should never show up in changes > 2) Changes shouldn't list a document twice > 3) This makes replication impossible since the reader tries to open missing > revisions. > Mostly for number (3) I'm marking this as critical. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.