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

Error messages and logging should not assume collection was dropped and recreated on epoch change

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc0, 4.5.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Sharding 2020-03-09, Sharding 2020-03-23

      Description

      There are a few places where we log or return an error message when a sharded collection's epoch changes that assume the collection was dropped and recreated (e.g. here). Previously this was correct, but as of 4.4 refining a collection's shard key can also change the epoch, so such messages/logs are misleading and should be updated.

        Attachments

          Activity

            People

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: