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

Don't allow resuming changeStreams after sharded collection drop

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2017-09-11, Repl 2017-10-02, Repl 2017-10-23

      Description

      Once a collection is dropped we lose all catalog information about it, which makes it impossible to extract the shard key on new cursors on sharded collections. So that means that resuming a sharded change stream after the collection was dropped won't work. We should make sure that fails gracefully.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              nathan.myers Nathan Myers
              Reporter:
              spencer Spencer Brody (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: