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

Use the 'chunkDataCommitted' failpoint for migration_critical_section_concurrency.js

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.4, 3.5.6
    • Affects Version/s: 3.5.5
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Sharding 2017-04-17
    • 0

      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.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: