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

Update error code in the stepdown hook.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 4.0.1
    • Fix Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
    • Operating System:
      ALL
    • Linked BF Score:
      9

      Description

      The error code for exceeding timeouts was determined to be ambiguous and was changed in SERVER-35031. We should update places that expect these errors in resmoke to handle the new error code. Right now the only place is in the stepdown hook.

      Note that there has been no change in pymongo throughout this process; it doesn't know about the new error code for ExceededTimeLimit and treats it as a generic OperationFailure. So the error handling code in stepdown.py should be changed to handle OperationFailure as well.

      We should also check that the code for the OperationFailure is indeed for ExceededTimeLimit(262) and still bubble up other errors.

      Affects master and 4.0 branches for now, but based on comments in SERVER-35031, it will be backported to earlier branches later.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-stm Backlog - Server Tooling and Methods (STM)
              Reporter:
              robert.guo Robert Guo
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: