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

ShardRegistry can temporarily forget newly added repl members

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.10
    • Fix Version/s: 3.3.14
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2016-08-29, Sharding 2016-09-19
    • Linked BF Score:
      0

      Description

      When the ReplicaSetMonitor detects a new member in a shard, it will update the ShardRegistry to contain the new member. However, a reload on the ShardRegistry can happen before the update gets propagated to the config servers. When this happens, the reload will not contain the new member, and this can cause the ShardRegistry to temporarily "forget" about the new member until the next reload after the config server gets updated with the new member.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              misha.tyulenev Misha Tyulenev
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: