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

Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2018-01-01, Sharding 2017-12-18, Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16, Sharding 2018-07-30, Sharding 2018-08-13, Sharding 2018-08-27, Sharding 2018-09-10
    • Case:

      Description

      This ticket was created as an overflow of SERVER-31056. Please refer to the comments there for more context.

      If after a migration commit on the config server, a donor shard fails to refresh its metadata, we clear the MetadataManager's metadata. We do this so that the next time the metadata is needed, a refresh will be triggered.

      However, if a request comes in with an UNSHARDED shardVersion, it will see empty metadata and the request will be allowed to go through without triggering a refresh.

      The linked SERVER-24960 contains test cases to validate the fix.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              kaloian.manassiev Kaloian Manassiev
              Participants:
              Votes:
              4 Vote for this issue
              Watchers:
              29 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: