[SERVER-44497] Aggregation: {"codeName" : "UnknownError"} Created: 08/Nov/19 Updated: 29/Mar/20 Resolved: 29/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Dheeraj Gunda | Assignee: | Dmitry Agranat |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
I have index on "claimId" field, I am aggregating to find duplicate values on "claimId" field. Aggregation with below query is working on Lower Environments (2Million documents). Failing with error on PROD enviroment (500 Million documents)
Aggregation Query:
Response with error:
|
| Comments |
| Comment by Dmitry Agranat [ 29/Mar/20 ] |
|
Hi dgunda@express-scripts.com, 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 Kelsey Schubert [ 19/Dec/19 ] |
|
Hi dgunda@express-scripts.com, 4.0.14 was released earlier today, would you please upgrade and let us know if it resolves the issue? Thanks, |
| Comment by David Storch [ 19/Nov/19 ] |
|
Hi dgunda@express-scripts.com, 4.0.14 has not yet been released. When it is released, the fix for Best, |
| Comment by Dheeraj Gunda [ 18/Nov/19 ] |
|
Hi Bernard/ David, The latest version I can download is 4.0.13, Can you share the link to download version 4.0.14 for Enterprise version? FYI, I can't upgrade to 4.2 version due to some dependencies. Thanks, Dheeraj
|
| Comment by Bernard Gorman [ 11/Nov/19 ] |
|
david.storch, dgunda@express-scripts.com: yes, this appears to be an instance of |
| Comment by Dheeraj Gunda [ 11/Nov/19 ] |
|
Hi Dave, Thanks for the suggestion, I will consider to upgrade to 4.0.14 |
| Comment by David Storch [ 11/Nov/19 ] |
|
I suspect that this is a duplicate of dgunda@express-scripts.com, Best, |
| Comment by Dheeraj Gunda [ 10/Nov/19 ] |
|
Hi Dima, Currently, MongoDB server version: 4.0.8 (Enterprise). Unable to reproduce the problem in lower environment (DEV, QA). As suggested I will try to run with traceExceptions parameter.
Thanks, Dheeraj
|
| Comment by Dmitry Agranat [ 10/Nov/19 ] |
|
Hi dgunda@express-scripts.com, Thank you for the report. I've looked at the code value.cpp:1344 but I don't see any assert there. Would it be possible to run the failing mongoD with the traceExceptions parameter? That would give us more information. Please note that the parameter will potentially generate a lot of logs so it can impact a performance. It would be great if the problem reproduces in a staging/testing environment. Also, please provide your MongoDB version. Thanks, |
| Comment by Dheeraj Gunda [ 08/Nov/19 ] |
|
Aggregation Query:
db.CLAIMS_ENTITY_COMM.aggregate([ , }}, ).forEach(function(doc) { doc.dups.shift(); db.CLAIMS_ENTITY_COMM_DUPS.insert(doc);});
|