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

Force the recipient shard to refresh its metadata after migration commit

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.1, 3.7.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Completed:
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2017-12-04

      Description

      In the current sharding migration protocol, the recipient shard finds about the migration commit lazily, when it gets hit with a query with a newer shard version.

      With the secondaries chunk aware project, where shards sync metadata from the config server and persist it locally, this laziness opens up a longer period where a crash of a shard's primary can render it unable to fetch the latest routing information from the config server.

      Because of this we should implement a best-effort attempt to force the recipient shard's primary to refresh the latest routing information after the migration commits.

        Attachments

          Activity

            People

            Assignee:
            dianna.hohensee Dianna Hohensee
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: