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

Replace MaxTimeMSExpired with ReadConcernMajorityNotAvailableYet during speculative majority

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication

      For v4.4 only.
      We wait 15 seconds waiting for the local snapshot to be majority committed then we return MaxTimeMSExpired on failure which is not a transient error so drivers don't retry on them specially that these 15 seconds got applied on commands that doesn't specify maxTimeMS in the first place for example: getMore running on pre-v5.0 versions with emrc=false

      SERVER-68328 made ReadConcernMajorityNotAvailableYet as a transient error and now it is a more suitable to be used here.

      SERVER-68328 should be backported first to v4.4.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            m.maher@mongodb.com Moustafa Maher
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: