[SERVER-71008] Fatal assertion 39001 BadValue: timestamp_transaction 22 Created: 02/Nov/22 Updated: 05/Dec/22 Resolved: 05/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.20 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Srikanta Patra | Assignee: | Yuan Fang |
| Resolution: | Done | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Hi Team,
There was a issue with our mongodb cluster. We have 4 Node cluster (verison 4.2.20) of which the primary got failover to one of the existing secondary server.
Upon analysing the logs, we found the same issue that we had raised couple of months back as part of https://jira.mongodb.org/browse/SERVER-55894 .
Below is the error log
|
| Comments |
| Comment by Yuan Fang [ 05/Dec/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. |
| Comment by Yuan Fang [ 21/Nov/22 ] |
|
We still need additional information to diagnose the problem. If this is still an issue for you, would you please check if any node running with enableMajorityReadConcern=false? if so, could you turn enableMajorityReadConcern: true (the default) or upgrade to 4.4? If not, or if the issue still persists after trying the steps advised above, could you 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. Regards, |
| Comment by Yuan Fang [ 02/Nov/22 ] |
|
Thank you for your report. We've seen issues that get similar WT error messages with enableMajorityReadConcern=false on 4.2, would you check if any node running with enableMajorityReadConcern=false? if so, could you turn enableMajorityReadConcern: true (the default) or upgrade to 4.4? If not, or if the issue still persists after trying the steps advised above, could you 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. Regards, |