Consider re-writing tests that inspect shards' database versions and expect shards to not be fully authoritative

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      The affected tests are:

      • jstests/sharding/transactions_stale_database_version_errors.js
      • jstests/sharding/database_versioning_all_commands.js

      We should consider re-writing or removing them (once 9.0 is the last LTS).

            Assignee:
            Unassigned
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: