resmoke Process::stop function should NOT wait for process to exit in windows

XMLWordPrintableJSON

    • DevProd Correctness
    • Fully Compatible
    • ALL
    • 11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Other parts of resmoke (such as ContinuousStepdown) assume stopping a process does not wait for it to exit cleanly. In this particular case, this is to immediately step up a secondary after the old primary has been shutdown, so that availability is restored as fast as possible.

      This is already the case for the non-Windows implementation, but for some unknown reason for mongod, in TERMINATE mode in Windows, resmoke waits up to 60 seconds. This causes sporadic test failures due to a primary not being found.

              Assignee:
              Mikhail Shchatko
              Reporter:
              Yujin Kang Park
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: