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

Use the 'chunkDataCommitted' failpoint for migration_critical_section_concurrency.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.5.5
    • Fix Version/s: 3.4.4, 3.5.6
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Sharding 2017-04-17
    • Linked BF Score:
      0

      Description

      The current implementation of migration_critical_section_concurrency.js uses a failpoint on the MigrationDestinationManager, which however cannot be blocked for more than 30 seconds because this is the timeout for migration commit. This causes build failures on slower machines and debug builds.

      Instead we should be using the 'hangBeforeLeavingCriticalSection' failpoint which is on the donor shard and can be held indefinitely.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: