[SERVER-32550] Drop of a non-existing collection on mongod should have the same behavior as mongos Created: 04/Jan/18 Updated: 09/Feb/23 Resolved: 09/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Sprint: | Execution Team 2023-02-20 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In the standalone and non-sharded case, calling dropCollection a second time fails. However, in order to be idempotent (which we want for metadata commands that are run on the config server in a sharded cluster), we would need a second drop command to also succeed. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 09/Feb/23 ] |
|
|
| Comment by Dianna Hohensee (Inactive) [ 03/Feb/23 ] |
|
This looks like the same request as |
| Comment by Kaloian Manassiev [ 01/Feb/22 ] |
|
Whoops, I didn't even look at the creation date and thought it just showed up |
| Comment by Kaitlin Mahar [ 31/Jan/22 ] |
|
Hey kaloian.manassiev, based on the date I actually filed this ticket during my new grad rotation on sharding! |
| Comment by Kaloian Manassiev [ 31/Jan/22 ] |
|
kaitlin.mahar, can you clarify what does it mean "metadata commands that are run on the config server" ? Are you suggesting that you are doing something that directly runs against the ConfigServer in Sharding? Because this is a loophole that we will soon be closed under PM-2689. |