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

Investigate why shard filtering metadata hook fails in catalog shard tests

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc1
    • None
    • None
    • None
    • Fully Compatible
    • v7.0
    • Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15

    Description

      Two catalog shard tests fail the checkShardFilteringMetadata hook at ShardingTest shutdown. Both fail because a secondary does not have filtering metadata in its shardingState response, and both involve either adding a shard or reconfiguring a node into a shard near the end of the test, so this may be the expected behavior, but we should verify this.

      jstests/sharding/reconfig_fails_no_cwwc_set_sharding.js

      jstests/sharding/implicit_default_write_concern_add_shard.js

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: