Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-926

Consider making ReadConcernMajorityNotAvailableYet a retryable error

    XMLWordPrintableJSON

Details

    • Spec Change
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • Retryability
    • None

    Description

      This came up during testing for Safe Replica Set Reconfig.

      During a safe reconfig, the primary will drop snapshots after writing down a new config document. If a read is issued on this node before it updates its snapshot, the server fails with ReadConcernMajorityNotAvailableYet.

      The node should eventually be able to update the committed snapshot through heartbeats (2 second interval), so the read will eventually succeed. It seems like we should treat this as a retryable error.

      Attachments

        Activity

          People

            Unassigned Unassigned
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: