TLA+ spec + jstest: ShardRegistry refresh must not stick on stale config secondary

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Companion artifact for SERVER-117349 (config server's ShardRegistry refresh indefinitely stuck on stale replica).

      Loopback refresh request lacks per-attempt timeout. TLA+ uses `HasPerAttemptDeadline` constant; weak fairness on retry + strong fairness on live-target pick.

      Files in worktree mongo-w4-13:

      • src/mongo/tla_plus/Sharding/ShardRegistryRefreshLiveness/{*.tla, MC.cfg, MC_bug.cfg, OWNERS.yml}
      • jstests/sharding/shard_registry_refresh_stuck_on_stale_replica.js (152 lines)

      Status: Draft.

            Assignee:
            Unassigned
            Reporter:
            Mehar Grewal
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: