Disable batch_write_command_update.js in FCV sharding upgrade/downgrade suite

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v9.0
    • CAR Team 2026-08-31
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Similar to SERVER-133182, batch_write_command_update.js intermittently fails in fcv_upgrade_downgrade_sharding_jscore_passthrough on enterprise-rhel8-debug-tsan.

      During background FCV upgrade/downgrade, auth-shard metadata recovery repeatedly clears and restores filtering metadata for the unsharded test collection. The maximum-size update then completes the first 20,024 operations but returns NoProgressMade for operation index 20024 and subsequent entries after exhausting mongos retry rounds.

      As this is expected, exclude the test from the FCV sharding suite until the metadata-transition behavior is stable under SERVER-98118.

            Assignee:
            Meryama Nadim
            Reporter:
            Meryama Nadim
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: