Rewrite replication state errors for movePrimary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      movePrimary can cause the RSM to report the wrong replica set as ReplicaSetNoPrimary on InterruptedDueToReplStateChange error. Rewrite the replicate state error for movePrimary to ensure it is not forwarded to remote caller similar to the fix for moveChunk in SERVER-91331.

      Since SERVER-91633 will not be implemented soon, this is a quick fix for BF-35277.

            Assignee:
            Unassigned
            Reporter:
            Kruti Shah
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: