Properly clean up resources in config_server_health_observer_crash.js

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      We create a ShardingTest during the course of this test but we do not guarantee we will stop it.

      We call stop() on the ShardingTest inside a try catch block and the catch block just swallows the exception.

      We should update this test to ensure we always call stop() when the test is done running.

            Assignee:
            Unassigned
            Reporter:
            Ben Gawel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: