-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
v7.0, v6.3
-
Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06
-
139
If a migration of the last chunk on a shard commits right before we stop migrations in the catalog manager, the refresh will not be sent to that shard (which is a donor of the migration). This means that we do not wait for the critical section on the donor shard, which can cause the ddl which called stopMigrations to continue when it should wait for the migration to complete.
Instead of sending the refresh to the shards that own chunks for the migration, we should send it to all shards.
- causes
-
SERVER-76394 Allow the setAllowMigrations refresh to be sent to all shards in a backportable way
- Closed