[SERVER-61756] Remove multiversion exception in ddl_ops_reported_on_current_op_command.js once 6.0 becomes last-lts Created: 29/Nov/21  Updated: 29/Oct/23  Resolved: 13/Jul/22

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-07-25
Participants:

 Description   

SERVER-57114 and SERVER-57113 added the ShardingDDLCoordinator in refineCollectionShardKey and movePrimary commands, however, these changes were not backported to 5.0 because it wasn't necessary, so, enabling the hangBeforeRunningCoordinatorInstance failpoint before checking if they show on the currentOp command cannot be done on multiversion suites until 6.0 becomes last-lts.



 Comments   
Comment by Githook User [ 13/Jul/22 ]

Author:

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

Message: SERVER-61756 Remove multiversion exception on ddl_ops_reported_on_current_op_command.js
Branch: master
https://github.com/mongodb/mongo/commit/f396ed9d5463904e835b5503b32b40e05ca7695d

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