You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/11 19:25:11 UTC
[jira] [Commented] (COUCHDB-3055) _changes queries using non
existent (moved) shard may rewind from zero
[ https://issues.apache.org/jira/browse/COUCHDB-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371460#comment-15371460 ]
ASF GitHub Bot commented on COUCHDB-3055:
-----------------------------------------
GitHub user iilyak opened a pull request:
https://github.com/apache/couchdb-fabric/pull/62
Use the correct sequence for shard replacement
Cherry-pick from Cloudant to 2.0
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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-fabric 44287-use-correct-sequence-for-shard-replacement
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fabric/pull/62.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #62
----
commit 5d0995966c117e3cf946216aff41116c2020c212
Author: Paul J. Davis <pa...@gmail.com>
Date: 2015-02-11T03:49:40Z
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)