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

Investigate if ShardRegistry reads on configsvrs can always be majority

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding EMEA
    • Sharding EMEA 2023-01-23

      Apparently there are circumstances where the ShardRegistry on config servers sometimes reads non-majority-committed writes to config.shards, based on:

      After SERVER-46202 makes the ShardRegistry causally consistent, it should be possible to eliminate any places where configsvrs do non-majority-commited ShardRegistry reads (thereby getting rid of ShardRegistry::clearEntries()).

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: