[SERVER-56198] Test all possible DDL coordinators conflict/join scenarios Created: 20/Apr/21  Updated: 06/Dec/22  Resolved: 25/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Fix Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-58099 Complete TODO listed in SERVER-56198 Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Implement a jstest that - for every DDL - uses multithreading + failpoints to:

  • Instantiate a DDL coordinator on a namespace NSS
  • Try to re-instantate the current operation on NSS (should join)
  • Try to instantate a conflicting operation on NSS (should fail)

The objective is to check that checkIfOptionsConflict is properly implemented for each DDL operation.



 Comments   
Comment by Githook User [ 29/Jun/21 ]

Author:

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

Message: SERVER-58099 Remove TODOs referencing SERVER-56198
Branch: master
https://github.com/mongodb/mongo/commit/7e7d7173a445214cf6bc66679921b1b61e2c4d9a

Comment by Kaloian Manassiev [ 25/Jun/21 ]

Won't fix this and will rely instead on the FSM suite coverage.

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