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

Hedge reads request hang when hedge read finishes first with MaxTimeMSExpired error

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc3, 4.7.0
    • Affects Version/s: 4.4.0-rc0
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Hide

      The failure is intermittent, appeared several times during testing.
      It appeared when a count or find request was submitted with a hedge read, then the primary request retried on StaleConfig error.

      Show
      The failure is intermittent, appeared several times during testing. It appeared when a count or find request was submitted with a hedge read, then the primary request retried on StaleConfig error.
    • Service arch 2020-04-20, Service arch 2020-05-04

      This is an intermittent failure that causes a read command to hang indefinitely when hedge reads are enabled and permitted i.e. as with readPreference mode nearest
      The root cause is that if a hedge read that expired with MaxTimeMSExpired error before the original request will be ignored but as it triggers the finish line the follow-up response will be ignored as well.

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Reporter:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: