[SERVER-67889] mongodb 4.4 secondary hang Created: 08/Jul/22  Updated: 04/Oct/22  Resolved: 04/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: jing xu Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File 89347.log     Text File currentOp.log    
Operating System: ALL
Participants:

 Description   

hello:
my replication is pss.but just only one slave hang .

MongoDB shell version v4.4.12
connecting to: mongodb://127.0.0.1:31004/admin?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session

{ "id" : UUID("f59fd32f-30cc-42db-b8e4-393c1a8384ed") }

MongoDB server version: 4.4.12

shard4:SECONDARY> rs.printSlaveReplicationInfo()
WARNING: printSlaveReplicationInfo is deprecated and may be removed in the next major release. Please use printSecondaryReplicationInfo instead.
source: mongotest11.prd.db:31004
syncedTo: Fri Jul 08 2022 09:38:12 GMT+0800 (CST)
2 secs (0 hrs) behind the primary
source: mongotest13.prd.db:31004
syncedTo: Fri Jul 08 2022 09:08:31 GMT+0800 (CST)
1783 secs (0.5 hrs) behind the primary
shard4:SECONDARY> show dbs;

i execute show dbs, it is hang.

i collect pstack for mongodb.
pstack 89347 >/tmp/89347.log



 Comments   
Comment by Edwin Zhou [ 04/Oct/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 Edwin Zhou [ 20/Sep/22 ]

We still need additional information to diagnose the problem. If this is still an issue for you, would you please archive (tar or zip) and upload to the secure upload portal:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Best,
Edwin

Comment by Edwin Zhou [ 29/Aug/22 ]

Hi 601290552@qq.com,

I apologize for the delay and I'm grateful for your patience as we investigate this issue.

If this problem has persisted, or if you were able to preserve the logs for when the incident occurred, could you attach additional diagnostic data to help us further investigate this problem? I've 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:

  • the mongod logs
  • the $dbpath/diagnostic.data directory (the contents are described here)

Thank you again for your patience.

Best,
Edwin

Generated at Thu Feb 08 06:09:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.