[SERVER-58868] Enable/Remove a commented moveChunk + AllowMigrations test Created: 27/Jul/21  Updated: 29/Oct/23  Resolved: 29/Jul/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.3, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-08-09
Participants:

 Description   

The goal of this task is to decide what to do with this commented test.

The test itself is doing something illegal: it directly modifies the allowMigrations flag without bumping the version. instead of using . I tried to use  the setAllowMigrations command instead but it didn't work.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 20/Aug/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-58868 Enable/Remove a commented moveChunk + AllowMigrations test

(cherry picked from commit 235da36e33a9b1b17fc3640fa9202598cca03883)
Branch: v5.0
https://github.com/mongodb/mongo/commit/d673ef4ac0953b0b32a4f077a558caec899f2067

Comment by Githook User [ 28/Jul/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-58868 Enable/Remove a commented moveChunk + AllowMigrations test
Branch: master
https://github.com/mongodb/mongo/commit/235da36e33a9b1b17fc3640fa9202598cca03883

Comment by Sergi Mateo Bellido [ 27/Jul/21 ]

Replacing the direct update of the allowMigrations flag by the setAllowMigrations command doesn't work because the test stops the moveChunk operation in the stage 5 (catch-up phase) after acquiring the critical section. As part of the setAllowMigrations command, we do a refresh on all shards that have chunks of that collection, but the refresh on the donor shard of the moveChunk op gets blocked because the critical section is acquired. That's the reason why we have a direct update of the flag on the test.

Generated at Thu Feb 08 05:45:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.