[SERVER-32568] The `migration_sets_fromMigrate_flag.js` test is not compatible with sharding continuous stepdown suite Created: 05/Jan/18  Updated: 30/Oct/23  Resolved: 09/Jan/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.1
Fix Version/s: 3.4.19, 3.6.3, 3.7.1

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6, v3.4
Sprint: Sharding 2018-01-15
Participants:
Linked BF Score: 0

 Description   

The `migration_sets_fromMigrate_flag.js` test occasionally fails in the continuous stepdown suite because the config server balancer steps down and cases moveChunk to run one time too many, which causes more 'i' entries to be present in the recipient's oplog.

Specifically, from the logs it can be seen that the migration, which fails due to 'failMigrationLeaveOrphans' happening twice due to the balancer recovery:

d23264| 2017-12-18T22:20:05.678+0000 W COMMAND  [conn29] failpoint: failMigrationLeaveOrphans set to: { mode: 1, data: {} }
...
d23264| 2017-12-18T22:20:08.319+0000 I SHARDING [migrateThread] failing migration after cloning 1 docs due to failMigrationLeaveOrphans failpoint
d23261| 2017-12-18T22:20:16.026+0000 W SHARDING [conn26] Chunk move failed :: caused by :: OperationFailed: Data transfer error: failing migration after cloning 1 docs due to failMigrationLeaveOrphans failpoint
...
d23264| 2017-12-18T22:20:16.210+0000 I SHARDING [migrateThread] failing migration after cloning 1 docs due to failMigrationLeaveOrphans failpoint

This test should be blacklisted from the continuous stepdown suite.



 Comments   
Comment by Githook User [ 16/Nov/18 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-32568 Blacklist migration_sets_fromMigrate_flag.js from the CSRS continuous stepdown suite

(cherry picked from commit a9d076d8642c13859588c3bc111b3c9af08cea2f)
Branch: v3.4
https://github.com/mongodb/mongo/commit/8d4c92a1cf12effd42a354e77c424e61c9afd72c

Comment by Githook User [ 13/Jan/18 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-32568 Blacklist migration_sets_fromMigrate_flag.js from the CSRS continuous stepdown suite

  • Make the test less resource intensive and verbose by lowering the
    number of spawned mongod instances
  • Add logging to dump the contents of the oplog on failure

(cherry picked from commit a9d076d8642c13859588c3bc111b3c9af08cea2f)
Branch: v3.6
https://github.com/mongodb/mongo/commit/9bf3b619f136bc7b4a0f3a2248a12889eccec8a7

Comment by Githook User [ 09/Jan/18 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-32568 Blacklist migration_sets_fromMigrate_flag.js from the CSRS continuous stepdown suite

Generated at Thu Feb 08 04:30:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.