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

ReshardingCoordinatorObserver destructor should only invariant if ReshardingCoordinatorService::run() is called

XMLWordPrintableJSON

    • Query Execution
    • Fully Compatible
    • ALL
    • v8.0
    • QE 2024-07-22
    • 0
    • 2

      In BF-30149 it was found that in very rare cases it is possible for ReshardingCoordinator Instance to be destroyed before Instance::run() is called by the POS framework as described in this comment. In this case the ReshardingCoordinator destructor would be called following which ReshardingCoordinatorOpObserver destructor would invariant on promises:

      ReshardingCoordinatorObserver::~ReshardingCoordinatorObserver() {
    stdx::lock_guard<Latch> lg(_mutex);
    invariant(_allDonorsReportedMinFetchTimestamp.getFuture().isReady());
    invariant(_allRecipientsFinishedCloning.getFuture().isReady());
    invariant(_allRecipientsReportedStrictConsistencyTimestamp.getFuture().isReady());
    invariant(_allRecipientsDone.getFuture().isReady());
    invariant(_allDonorsDone.getFuture().isReady());
}

      We should pass through the invariant checks if Instance::run() is not called.

            Assignee:
            kristina.znam@mongodb.com Kristina Znam
            Reporter:
            abdul.qadeer@mongodb.com Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: