[SERVER-64034] Replica node failure due to script execution Created: 28/Feb/22 Updated: 02/Jun/22 Resolved: 29/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anush Chinoian | Assignee: | Edwin Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Greetings, we need assistance in determining the cause of our issue with Mongo cluster. Cluster settings:
Static hostname: m1-prod-vm-db-mongo02 During the execution of the script which updates the data in collections we encountered a failure of one of replica nodes. (update.txt) To repair the cluster we performed the following:
The logs during the failure (logs.txt) |
| Comments |
| Comment by Edwin Zhou [ 29/Mar/22 ] |
|
We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. Best, |
| Comment by Edwin Zhou [ 10/Mar/22 ] |
|
Have you experienced this problem persisting? We look forward to receiving the requested data if this problem is still an issue for you. Best, |
| Comment by Dmitry Agranat [ 03/Mar/22 ] |
|
anush.chinoian@gmail.com, unfortunately, w/o logs/diagnostics.data it is not possible to determine the cause of the issue. You can use this Jira search to inspect all potential causes for the reported issue. |
| Comment by Anush Chinoian [ 03/Mar/22 ] |
|
Thanks for the reply. If the problem persists, we will upload diagnostic information and logs without personal data. But based on the current incident, can you tell what could have been the cause in principle (for example, one of the bugs fixed in later versions)? |
| Comment by Dmitry Agranat [ 01/Mar/22 ] |
|
Thanks for the update anush.chinoian@gmail.com, if this happens again, please save the requested data and upload it to the secure uploader. |
| Comment by Anush Chinoian [ 01/Mar/22 ] |
|
We have a version 4.2.2 |
| Comment by Anush Chinoian [ 28/Feb/22 ] |
|
Sorry, but I can't download the full mongod.log logs because we use Mongodb as an audit database and the logs contain personal data. The problem was discovered on 21.02, on diagnostic.data files only for 24.02 and beyond |
| Comment by Dmitry Agranat [ 28/Feb/22 ] |
|
Does the issue happen when MongoDB is being deployed on the latest version in 4.2, which is currently 4.2.18? In order to investigate this issue, we will need some additional information. Would you please archive (tar or zip) the full mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) from all members of this replica set covering the time of this event 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, |