[jira] [Commented] (COUCHDB-2937) _changes queries using last_seq after a shard move may rewind from zero

["Benjamin Bastian (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111063#comment-15111063 ] 

Benjamin Bastian commented on COUCHDB-2937:
-------------------------------------------

Fixed by: https://github.com/apache/couchdb-fabric/pull/36

> _changes queries using last_seq after a shard move may rewind from zero
> -----------------------------------------------------------------------
>
>                 Key: COUCHDB-2937
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2937
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>            Reporter: Benjamin Bastian
>            Assignee: Benjamin Bastian
>
> Currently, the last_seq of a _changes query doesn't contain the epoch node of the shard. If the shard has been moved, _changes queries using the last_seq of a prior _changes query will route shard queries to the incorrect node and therefore rewind from zero.
> last_seq should include the epoch node so subsequent _changes?since=<last_seq> queries don't rewind from zero.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)