[SERVER-60751] move_chunk_critical_section_non_internal_client_abort.js does not consider config server stepdowns Created: 15/Oct/21  Updated: 29/Oct/23  Resolved: 02/Nov/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.2 Desired
Fix Version/s: 5.2.0, 5.0.5, 5.1.1

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-59891 Replace the coverage from sharding_co... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.1, v5.0
Sprint: Sharding EMEA 2021-11-15
Participants:
Linked BF Score: 35

 Description   

After SERVER-47324 the collMod command requested to a shard directly will cause any ongoing migration to be aborted, in order to test this move_chunk_critical_section_non_internal_client_abort.js relies that a moveChunk command issued by a user will fail if executed with a concurrent collMod, however, in the sharding_csrs_continuous_config_stepdown suite we might find the following scenario:

1. A router sends the _configsvrMoveChunk command to a config server
2. The config server sends the moveChunk command to a shard
3. The move chunk waits in the moveChunkHangAtStep5 failpoint (before committing the migration on the config server)
4. We execute the collMod command directly on the shard
5. The current migration is aborted
6. The config server steps down before finishing the command
7. The new config server primary retries the command

Causing the test to fail, even though we're successfully aborting the migration on the donor shard at point 5 as expected. We should blacklist this test from the sharding_csrs_continuous_config_stepdown suite.



 Comments   
Comment by Githook User [ 12/Nov/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-60751 Add does_not_support_stepdown tag to move_chunk_critical_section_non_internal_client_abort.js

(cherry picked from commit e00478473ddacb362f172dab583bf572ce512ea2)
Branch: v5.1
https://github.com/mongodb/mongo/commit/681b75673ada623b61d6e2f5987c2284559557d8

Comment by Githook User [ 08/Nov/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-60751 Add does_not_support_stepdown tag to move_chunk_critical_section_non_internal_client_abort.js

(cherry picked from commit e00478473ddacb362f172dab583bf572ce512ea2)
Branch: v5.0
https://github.com/mongodb/mongo/commit/a8ed66f536d775ded1bab37ea84df8104f094893

Comment by Githook User [ 02/Nov/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-60751 Add does_not_support_stepdown tag to move_chunk_critical_section_non_internal_client_abort.js
Branch: master
https://github.com/mongodb/mongo/commit/e00478473ddacb362f172dab583bf572ce512ea2

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