[SERVER-57642] Invariant Failure on src/mongo/db/query/plan_yield_policy.cpp 75 | Aborting Created: 11/Jun/21 Updated: 29/Oct/23 Resolved: 13/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.14, 4.4.6, 4.0.25, 5.0.0-rc8 |
| Fix Version/s: | 4.2.16, 4.4.8, 5.0.2, 4.0.27, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Paulo Pereira | Assignee: | Mihai Andrei |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v5.0, v4.4, v4.2, v4.0
|
||||||||||||
| Sprint: | Query Execution 2021-07-12, Query Execution 2021-07-26 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 84 | ||||||||||||
| Description |
|
We are having this issue on MongoDB 4.2.14 after firing an application doing several tasks on the BD.
|
| Comments |
| Comment by Githook User [ 29/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: |
| Comment by Githook User [ 27/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: (cherry picked from commit d2448e3da8a121955d5cb2bdbb50c8f2c1e9f6ca) |
| Comment by Githook User [ 21/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: (cherry picked from commit d2448e3da8a121955d5cb2bdbb50c8f2c1e9f6ca) |
| Comment by Githook User [ 20/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: (cherry picked from commit d2448e3da8a121955d5cb2bdbb50c8f2c1e9f6ca) |
| Comment by Githook User [ 20/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: (cherry picked from commit d2448e3da8a121955d5cb2bdbb50c8f2c1e9f6ca) |
| Comment by Githook User [ 14/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: |
| Comment by Githook User [ 13/Jul/21 ] |
|
Author: {'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}Message: |
| Comment by Mihai Andrei [ 07/Jul/21 ] |
|
Hi paulo.pereira@cmas-systems.com Thanks for reaching out and reporting your issue! After some investigation, this does appear to be a server bug and we are currently working on a fix. Please continue to watch this ticket for updates. Regards, |
| Comment by Paulo Pereira [ 14/Jun/21 ] |
|
Yes Dmitry |
| Comment by Dmitry Agranat [ 14/Jun/21 ] |
|
Thanks paulo.pereira@cmas-systems.com, just to clarify, is this is single-member replica set deployment and it was always like this? |
| Comment by Paulo Pereira [ 14/Jun/21 ] |
|
Done |
| Comment by Dmitry Agranat [ 14/Jun/21 ] |
|
Let's try one more time, this link |
| Comment by Paulo Pereira [ 14/Jun/21 ] |
|
Hi Dmitry, |
| Comment by Dmitry Agranat [ 14/Jun/21 ] |
|
Hi paulo.pereira@cmas-systems.com, here is a new link to secure uploader |
| Comment by Paulo Pereira [ 14/Jun/21 ] |
|
Sorry, I've found the correct diagnostic.data folder to send you. "This shared file or folder link has been removed or is unavailable to you." Can you provide another support uploader location, please? Thank You Paulo Pereira |
| Comment by Dmitry Agranat [ 14/Jun/21 ] |
|
There is something wrong with the data you've uploaded. The diagnostic.data is from 2019 and for MongoDB 4.2.0 and the log file is from 2021 and MongoDB 4.2.14. We will need both diagnostic.data and mogod log from the same source and same event. It will be useful if you can reproduce this issue and collect the requested information. Please note that when uploading the diagnostic.data, please upload the whole archive rather than a certain .metric file. |
| Comment by Paulo Pereira [ 14/Jun/21 ] |
|
Hi Dmitry, The diagnostic.data folder that I sent you is the one that sits on the MongoDB server in question, I don't have other. Thank You |
| Comment by Dmitry Agranat [ 14/Jun/21 ] |
|
Thanks paulo.pereira@cmas-systems.com, can you attach the diagnostic.data that covers the recent event? The one you've attached is from 2019. You can upload the whole diagnostic.data archive into the secure portal I provided in my previous comment. Also, do you still have the logs from 4.2.11 or when this issue was first originated? |
| Comment by Paulo Pereira [ 13/Jun/21 ] |
|
Hi Dmitry, In the meanwhile I've upgraded MongoDB version to 4.2.14, but the problem persists. Thank You |
| Comment by Dmitry Agranat [ 13/Jun/21 ] |
|
Hi paulo.pereira@cmas-systems.com, The backtrace has a 4.2.11 version, so the mentioned 4.2.14 MongoDB version is a typo? Would you please archive (tar or zip) the mongod.log files covering the incident and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location? Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Thanks, |