Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-32088

ChangeStream resumeAfter does not work on sharded collections if not all shards have chunks for the collection

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Query 2018-04-23, Query 2018-05-07, Query 2018-05-21, Query 2018-06-04
    • 26

    Description

      Taken from a comment on SERVER-32029:

      If a collection is sharded but not present on all shards, then some shards will not know about the collection, and will also mistakenly error upon resuming because of this. This bug is actually harder to fix, because it's hard to know whether the collection doesn't exist because it was dropped, or whether it doesn't exist because you don't own any chunks for it.

      Attachments

        Issue Links

          Activity

            People

              nicholas.zolnierz@mongodb.com Nicholas Zolnierz
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: