[SERVER-53083] collStats results depend on topology and option. Created: 25/Nov/20 Updated: 29/Oct/23 Resolved: 23/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sam Mercier | Assignee: | Ruslan Abdulkhalikov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | 1) Setup a mongod instance.
3) Start a sharded cluster (e.g. by running
in the mongo shell with the `--nodb` option).
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Query 2020-12-28, Query 2021-01-25, Query Optimization 2021-02-22, Query Optimization 2021-03-08, Query Optimization 2021-03-22, Query Optimization 2021-04-05 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
In three additional cases (beyond the ones described in Currently, if one attaches to a standalone instance of mongo, one will receive the NamespaceNotFound error code if one asks for collStats with the queryExecStats or storageStats options on a namespace that doesn't exist (e.g. "dne"). Additionally, one will receive a numeric error code if one passes an unknown option (e.g. "unknown"). However, if one connects to a mongos the NamespaceNotFound errors will be suppressed by the mongos instance if one pass such options to a namespace that doesn't exist. Additionally, because we don't validate that the options passed to collStats are correct when we do a "light parse" of the pipeline we actually get a NamespaceNotFound error when we get the routing info which then gets suppressed by the same code path if one asks for collStats on a collection that doesn't exist with an unknown option. Resolution of this ticket should include: |
| Comments |
| Comment by Githook User [ 23/Mar/21 ] |
|
Author: {'name': 'ruslan.abdulkhalikov', 'email': 'ruslan.abdulkhalikov@mongodb.com', 'username': 'rusabd1'}Message: |
| Comment by Joel Redman (Inactive) [ 07/Jan/21 ] |
|
Still trying to get my first build. But sure! via [1]Newton Mail [2]Charlie Swanson assigned an issue to [3]Joel Redman
[4]Joel Redman I'm assigning this to you to track for the next sprint. Please take a look after you get to a good stopping point and/or blocked with your current ticket. [5]Core Server / [6][7]SERVER-53083 Change By: [9]Charlie Swanson [10] [11]Add Comment This message was sent from MongoDB's issue tracking system. To respond to this ticket, please login to [12]jira.mongodb.org using your JIRA, MongoDB Cloud Manager, or MongoDB Atlas credentials. |
| Comment by Charlie Swanson [ 07/Jan/21 ] |
|
joel.redman I'm assigning this to you to track for the next sprint. Please take a look after you get to a good stopping point and/or blocked with your current ticket. |