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

Make cluster_time_across_add_shard.js resilient to slow RSM updates

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability
    • 20

    Description

      With TestData.configShard == true, cluster_time_across_add_shard.js https://github.com/mongodb/mongo/blob/7d3620f267bab213beccbd240a6bd3c0deb89892/jstests/sharding/cluster_time_across_add_shard.js#L172, which uses the config server's replica set monitor to target itself (via the addShard command run internally), and this can fail if the config server's RSM is stale. This is much more likely with the older SDAM RSM protocol than the newer streamable one, so when the test runs with the older protocol, it should retry on those errors or use a test helper to wait until the config primary has updated its RSM before running the transition command.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: