Loading...

XML

Word

Printable

JSON

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Backport Requested:

v7.3, v7.0, v6.0, v5.0
Sprint:
Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05
Linked BF Score:
134
Story Points:
3

We have seen several issues while running $out and movePrimary concurrently. Here are some of them:

The aim of this ticket is to test this scenario to prevent future problems.

causes

SERVER-89251 Revert concurrent movePrimary and aggregations test from v7.0 and v6.0

depends on

SERVER-78850 $out may fail with CursorNotFound if a movePrimary is ongoing

SERVER-81371 movePrimary's clone phase failure may be retried indefinitely if database contains sharded views

SERVER-83874 Move primary operation doesn't drop db.system.views on the donor

is testing

SERVER-76848 [false alarm] $out does not ensure the node remains primary throughout the internal rename

SERVER-78851 movePrimary may fail on clone phase if $out runs concurrently

(1 is testing)