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

ReadConcernMajorityNotAvailableYet errors from ShardRegistry must be retried

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.3.0, 5.1.2, 5.0.6, 5.2.0-rc3
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.2, v5.1, v5.0, v4.4
    • Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27
    • 46

    Description

      ShardRegistry::reload() must never fail with ReadConcernMajorityNotAvailableYet but rather retry reading from the config server.

      The retries should happen with exponential backoff capped to 30 seconds, in order to don't overwhelm the CSRS but - at the same - not retry after too long.

      Attachments

        Issue Links

          Activity

            People

              pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
              pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: