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

Remove need for reshardingCoordinatorCanEnterCriticalImplicitly failpoint from ReshardingTest fixture

    XMLWordPrintable

Details

    • Fully Compatible
    • Sharding 2021-05-17
    • 2

    Description

      The reshardingCoordinatorCanEnterCriticalImplicitly failpoint was introduced in SERVER-53916 to sidestep the interdependency with SERVER-53920. Now that both SERVER-53916 and SERVER-53920 are both committed, it shouldn't be necessary to have this failpoint enabled in the ReshardingTest fixture by default and realistically to even have this failpoint at all.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-56206 Make the estimation of remaining time in resharding more robust

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-53916 Create commitReshardCollection command

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-53920 Periodically obtain remainingOperationTimeEstimatedMillis estimates from recipients for use by the ReshardingCoordinator

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              janna.golden@mongodb.com Janna Golden
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: