[
https://issues.apache.org/jira/browse/COUCHDB-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371483#comment-15371483
]
ASF subversion and git services commented on COUCHDB-3055:
----------------------------------------------------------
Commit 5d0995966c117e3cf946216aff41116c2020c212 in couchdb-fabric's branch
refs/heads/master from [~paul.joseph.davis]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-fabric.git;h=5d09959 ]
Use the correct sequence for shard replacement
The call to unpack the since sequence for _changes incorrectly filtered
the value for any shard that didn't exist. This means that any shard
that was moved ended up requiring a complete rescan which is a bug. This
just sets the update sequence to the range of the shard being replaced
rather than zero.
COUCHDB-3055
> _changes queries using non existent (moved) shard may rewind from zero
> ----------------------------------------------------------------------
>
> Key: COUCHDB-3055
> URL: https://issues.apache.org/jira/browse/COUCHDB-3055
> Project: CouchDB
> Issue Type: Bug
> Reporter: ILYA
>
> The call to unpack the since sequence for _changes incorrectly filtered
> the value for any shard that didn't exist. This means that any shard
> that was moved ended up requiring a complete rescan which is a bug. This
> just sets the update sequence to the range of the shard being replaced
> rather than zero.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
