Move primary coordinator silently exit on errors

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v7.0
    • Hide

      1. Start a movePrimary and reach the commit phase
      2. Step down the node, wait until the coordinator resumes
      3. Cause any failure in the exit critical section phase, like for example, step down the config server

      Show
      1. Start a movePrimary and reach the commit phase 2. Step down the node, wait until the coordinator resumes 3. Cause any failure in the exit critical section phase, like for example, step down the config server
    • Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07
    • 134
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      After SERVER-73929 we use the onError chain in order to cleanup any problem caused in the clone phase. Unfortunately, the code is missing a return status; statement, causing that any error after the commit phase to not be retried, which could lead for example to maintain the critical section even after finishing the move primary command.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: