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

_configsvrCommitChunkMigration keeps retrying to do a local write after stepdown

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 6.1.0-rc0
    • Component/s: None
    • Labels:
      None
    • ALL
    • Hide

      ./buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=.50 --suite=sharding --log=file jstests/sharding/repro-server-67009.js

      Show
      ./buildscripts/resmoke.py run --storageEngine=wiredTiger --storageEngineCacheSizeGB=.50 --suite=sharding --log=file jstests/sharding/repro-server-67009.js
    • 35

      SERVER-65836 changed the way chunk migration commit modifies the config.chunks documents: Now it is done using the internal transactions API. This uses SyncTransactionWithRetries, which will retry to commit the transaction until it succeeds. This goes directly to the service_entry_point. In case of stepdown, this will keep retrying locally and getting the same NotPrimary errors repeatedly, without returning the error to the caller node. Returning to the caller node is desirable to give it the change to retarget the write to the proper configsvr primary.

      _configsvrCommitChunkMigration should immediately fail and return the error to the client instead.

        1. 0001-Repro-SERVER-67009.patch
          5 kB

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: