[SERVER-57861] Exclude move_chunk_allowMigrations.js from does_not_support_stepdowns suite Created: 21/Jun/21  Updated: 29/Oct/23  Resolved: 22/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-upkeep
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-06-28
Participants:
Linked BF Score: 38

 Description   

The _configsvrSetAllowMigrations command was invoked immediately after the primary Config Server was step down, causing a command interruption. The error is expected in this context, but it's not expected to invoke the _configsvrSetAllowMigrations command in such a scenario.

The solution consists in excluding this test from the does_not_support_stepdowns suite.



 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 [ 22/Jun/21 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-57861 Exclude move_chunk_allowMigrations.js from does_not_support_stepdowns suite
Branch: v5.0
https://github.com/mongodb/mongo/commit/b26580dfde7dcf4889b3485a7223431de6a64224

Comment by Githook User [ 21/Jun/21 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-57861 Exclude move_chunk_allowMigrations.js from does_not_support_stepdowns suite
Branch: master
https://github.com/mongodb/mongo/commit/3bd15beed5027089646922447fb11cef5e1c02b5

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