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

Ensure sharding tests shut down with all nodes up

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Cluster Scalability Priorities, Cluster Scalability 2024-12-23, Cluster Scalability 2025-01-20

      When shutting down a ShardingTest, we often run validation hooks, like validating sharding metadata is correct. These hooks generally assume all servers in every started replica set are available, which isn't true in all tests. We usually work around this by manually marking tests to skip certain problematic validations, e.g. here where we manually disable 4 validations. Instead we can add an assertion that every member in ShardingTest is running when ShardingTest#stop() is called, forcing existing tests and any new ones to restart any nodes they shut down before ending the test, which may make tests run slightly longer, but should lead to fewer BFs and make adding new validations easier.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: