[SERVER-32712] CommandNotSupportedOnView error with aggregation on views Created: 16/Jan/18 Updated: 21/Mar/18 Resolved: 16/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Querying |
| Affects Version/s: | 3.4.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | yang feng | Assignee: | Mark Agarunov |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
5 nodes with : |
||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | 1. import lots of data( about 100 millions documents) into a sharded collection. |
| Participants: |
| Description |
|
I got the "codeName" : "CommandNotSupportedOnView" error while doing aggregation on views. This occurs from time to time, most often when right after importing lots of data. For now, it seems that restarting the mongos will fixed it temporarily. view creation info from system.views:
aggregation commands:
return:
And: I have some views whose data needs to do a full collection refresh every day, for example there's a collection named "COL", I import the new data to a new collection name "COL_20180115" on 2018-01-15, then recreate the view named "COL" pointing to the daily new collection. Since renaming collection was not supported on sharded collections, using views was the only option I came up with. |
| Comments |
| Comment by Kelsey Schubert [ 16/Feb/18 ] |
|
Hi dy, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Mark Agarunov [ 01/Feb/18 ] |
|
Hello dy, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide:
Thanks, |
| Comment by Mark Agarunov [ 16/Jan/18 ] |
|
Hello dy, Thank you for the report. To get a better idea of what may be causing this error, could you please provide the complete logs from all affected mongod and mongos nodes when this issue is present? This should give some insight into why these commands are failing on views. Additionally could you please provide an example of the structure of the documents that are being inserted? This should help us reproduce the issue. Thanks, |