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

Mongos should respect the client Op timeout without relying on mongod to do so

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 4.0.23
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      In the HELP ticket repro, artificial fault injection was made to simulate disk error on mongod. While mongod was not capable to respect the operation timeout because the thread was blocked indefinitely on disk operation. Additional fault injection was made to simulate the operation timeout at mongos and that resulted in much slower connection buildup than without timing out the operations.

      It should be assumed that interrupting a thread stuck waiting on socket reply should me much easier than interrupting the thread stuck on faulty disk I/O, because the TCP connection is still perfectly healthy. In Enterprise binaries, the problem of faulty disk on mongos is solved by Watchdog.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-servicearch Backlog - Service Architecture
              Reporter:
              andrew.shuvalov Andrew Shuvalov
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: