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

Failures in txn_two_phase_commit_coordinator_shutdown_and_restart.js may go undetected by resmoke/Evergreen

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Cluster Scalability
    • ALL

      txn_two_phase_commit_coordinator_shutdown_and_restart.js invokes a potentially asserting command through startParallelShell(), but it is not verifying its correct execution by checking the exit code of the spawned process.

      As a consequence of this, any exception raised within the code section run in parallel won't be detected by resmoke/evergreen as a test failure - instead, the following will be logged:

      [js_test:txn_two_phase_commit_coordinator_shutdown_and_restart] sh20176| uncaught exception: Error: command did not fail with any of the following codes [ 50 ] {
      [js_test:txn_two_phase_commit_coordinator_shutdown_and_restart] sh20176| 	"ok" : 0,
      [js_test:txn_two_phase_commit_coordinator_shutdown_and_restart] sh20176| 	"errmsg" : "Could not find host matching read preference { mode: \"primary\" } for set txn_two_phase_commit_coordinator_shutdown_and_restart-rs0",
      

      (link to the occurrence: https://logkeeper.mongodb.org/lobster/build/9d6a13e85dbfb9cdaec07f4c61b0fddc/test/60e5348354f2481be6ee9219#bookmarks=0%2C7768%2C7770%2C11130&f~=000~sh%5Cd%2B%5C%7C).

      This other test may be used as a reference for implementing a fix.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: