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

ReshardingDataReplication may emplace _consistentButStale more than once

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • Sharding 2021-04-05
    • 155
    • 1

      It is possible for _consistentButStale.emplaceValue() to be called after ensureFulfilledPromise(_consistentButStale, originalError) has already been called. This is due to whenAllSucceed() returning a future ready with an error status if one of the data replication components has errored. ReshardingDataReplication should instead call ensureFulfilledPromise(_consistentButStale, originalError) after waiting for the future return by whenAll() to become ready.

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: