_configsvrMoveChunk does not gossip the proper operationTime back to the router

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15, Sharding EMEA 2021-11-29
    • 59
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Since after SERVER-60336 _configsvrMoveChunk runs the code that send the commands to the shards in a different thread client than the command and then joins it, the original command thread is not made aware of the operationTime returned from the shards, and thus it does not gossip it back to the router.

      To fix it, after joining the thread, the original command thread must set its lastOpTime to the system's lastOpTime

              Assignee:
              Paolo Polato
              Reporter:
              Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: