[SERVER-73972] mongodb 4.4 secondary replication hang Created: 14/Feb/23 Updated: 27/Feb/23 Resolved: 27/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | jing xu | Assignee: | Yuan Fang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Engines
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
1、i check replication info that i find the one secondary lag more than 9000s { , , "opid" : -1523928877, }, }, , , , , } } ], }, , }, }, }, }, }, } } |
| Comments |
| Comment by Yuan Fang [ 27/Feb/23 ] |
|
Hi 601290552@qq.com, After reviewing the FTDC you provided, we noticed an increase in update conflicts following the point in time when the secondary began to lag. Based on the comment from haribabu.kommi@mongodb.com, we recommend that you upgrade to the latest version of MongoDB 4.4 (currently 4.4.18). We will be closing this ticket for now, but if the issue persists even after upgrading to the latest version, please let us know by following up here, and we will reopen the ticket. Regards, |
| Comment by Haribabu Kommi [ 27/Feb/23 ] |
|
Thanks to yuan.fang@mongodb.com for the details and 601290552@qq.com for the bug report. Usually, the update conflicts are possible when there are any active transactions running in the system. Still, from the FTDC data, I couldn't find any active transactions in the system. While going through the couple of bugs that are fixed in WiredTiger, I found a bug The Server version that reproduced this bug is running MongoDB 4.4.12 version. Updating the MongoDB server to the latest supported version could fix this problem. |
| Comment by jing xu [ 23/Feb/23 ] |
|
hi: |
| Comment by Yuan Fang [ 22/Feb/23 ] |
|
Hi 601290552@qq.com, Thank you for providing the FTDC. While we are investigating this, could you also please provide the mongod.log that covers the time when the incident occurred, as requested in our previous comment? upload portal is still available for you to use. Regards, |
| Comment by jing xu [ 21/Feb/23 ] |
|
hi: |
| Comment by Yuan Fang [ 14/Feb/23 ] |
|
Hi 601290552@qq.com, Thank you for your report. Could you provide additional diagnostic data to help us further investigate this problem? I created a secure upload portal for you. Files uploaded to this portal are hosted on Box, are visible only to MongoDB employees, and are routinely deleted after some time. For each node in the replica set spanning a time period that includes the incident, would you please archive (tar or zip) and upload to that link:
Regards, |