[SERVER-57128] Router's retry of successful DDL must not spawn a new coordinator Created: 21/May/21 Updated: 06/Dec/22 Resolved: 26/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | PM-1965-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, it is possible to end up in the following scenario:
Objective of this ticket is to ensure that the retry arriving to the new primary results in a noop with the router receiving a proper successful response. |
| Comments |
| Comment by Githook User [ 15/Nov/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Kaloian Manassiev [ 24/May/21 ] |
|
I don't think we can possibly fix this scenario unless the client starts attaching LSID/txnNumber just like retryable writes. It is essentially a retryable DDL. Even if we fix it at the level of MongoS < - > MongoD, the same issue exists between Client < - > MongoD. I propose that we close this ticket, since it is no different than DDL against a replica set. |