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

Hedged reads should ignore stale errors

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 4.4.1
    • 4.9.0
    • Networking
    • Fully Compatible
    • ALL
    • Hide
      • An insert occurs and it's majority written, but haven't been replicated on one of the nodes
      • A count operation is performed
      • The fastest request is the one to the node that haven't replicate the insert yet
      • A StaleDB or StaleShardVersion error is thrown
      Show
      An insert occurs and it's majority written, but haven't been replicated on one of the nodes A count operation is performed The fastest request is the one to the node that haven't replicate the insert yet A StaleDB or StaleShardVersion error is thrown
    • 45

    Description

      Imagine the following scenario with a sharded cluster with 1 router, and 1 shard with 3 nodes and hedged reads active:

      • An insert occurs and it's majority written, but haven't been replicated on one of the nodes
      • A count operation is performed
      • The fastest request is the one to the node that haven't replicate the insert yet
      • A StaleDB or StaleShardVersion error is thrown

      The current code only ignores MaxTimeMSExpired errors so a stale error will make the operation fail.

      Attachments

        Activity

          People

            jaume.moragues@mongodb.com Jaume Moragues (Inactive)
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: