[SERVER-36317] Mongos returns true when attempting to drop non-existent database Created: 26/Jul/18 Updated: 27/Oct/23 Resolved: 27/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Aprahamian (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
With the following command:
Sending the following command to a mongod (replicaset or standalone) results in an error ns not found. Sending the command to a mongos returns ok: 1. Is this inconsistency expected? |
| Comments |
| Comment by Githook User [ 14/Jan/19 ] |
|
Author: {'username': 'daprahamian', 'email': 'dan.aprahamian@gmail.com', 'name': 'Dan Aprahamian'}Message: test(drop): fixing drop assertions for sharded tests As tracked in |
| Comment by Githook User [ 24/Sep/18 ] |
|
Author: {'name': 'Dan Aprahamian', 'email': 'dan.aprahamian@gmail.com', 'username': 'daprahamian'}Message: test(drop): fixing drop assertions for sharded tests As tracked in |
| Comment by Gregory McKeon (Inactive) [ 27/Aug/18 ] |
|
daniel.aprahamian it seems we failed to mark the ticket that introduced this change, |
| Comment by Esha Maharishi (Inactive) [ 27/Aug/18 ] |
|
Yes, it's expected, though it is a change as of 4.0. As part of "move metadata commands to the config server", we had to make metadata commands retryable in a cluster, so that mongos can retry the command on receiving a NotMaster-esque error from the config server the mongos was talking to. |
| Comment by Githook User [ 01/Aug/18 ] |
|
Author: {'name': 'Dan Aprahamian', 'email': 'dan.aprahamian@gmail.com', 'username': 'daprahamian'}Message: test(drop): fixing drop assertions for sharded tests As tracked in |