You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by "Benjamin Bastian (JIRA)" <ji...@apache.org> on 2016/01/15 21:51:39 UTC

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

Benjamin Bastian created COUCHDB-2937:
-----------------------------------------

             Summary: _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


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)