[SERVER-70138] DHandle could not be released after close_idle_time Created: 30/Sep/22 Updated: 21/Oct/22 Resolved: 21/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | qingtao sun | Assignee: | Yuan Fang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
We have environment with many tables. The file open number becomes very high. Even after we stopped any operation, the file open number did not go lower. I set close_idle_time as 10 seconds, the handle should be released after 10 seconds and hence most of the file should be closed |
| Comments |
| Comment by Yuan Fang [ 21/Oct/22 ] |
|
Thank you for providing the diagnostic data. Looking at the FTDC, I think the reason for seeing the high active dhandles connections is because the dhandles closed rate is less than the new connection open rate. If I understand correctly, setting close_idle_time as 10 seconds means: file handles need to be idle for 10 seconds before attempting to close it. In other words: connections wouldn't be closed if they kept active. As for the root cause of it, I don't have a certain answer, unfortunately. Please note that MongoDB 4.0 reached end of life in April 2022 and is no longer supported. Can you please upgrade to MongoDB v4.2+ and see if it solves the issue? For any further questions in regard to this issue, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Regards, |
| Comment by qingtao sun [ 12/Oct/22 ] |
|
Hello, Yuan Fang Affected mongodb version: 4.0.28. log file already uploaded. Thanks, |
| Comment by qingtao sun [ 11/Oct/22 ] |
|
Hello, Yuan Fang I am using mongodb version 4.0.28. Thanks, |
| Comment by qingtao sun [ 10/Oct/22 ] |
|
Hello, Yuan Fang I uploaded the log and diagnostic data on linux successfully. Please help Thanks. |
| Comment by qingtao sun [ 10/Oct/22 ] |
|
I have tried different ways already, here is the screenshot without quote. |
| Comment by Yuan Fang [ 05/Oct/22 ] |
|
Thank you for providing more information. In regard to the uploading issue, I would suggest you double-check your command by comparing it with the curl snippet provided in the support uploader location. It seems no single quote is required around file=@<filename>, can you try with these removed and see if that works? And, could you let us know the MongoDB version? Thanks, |
| Comment by qingtao sun [ 05/Oct/22 ] |
|
Hello, |
| Comment by qingtao sun [ 05/Oct/22 ] |
|
Hello, Yuan Rang Thanks a lot for looking into this issue. Here is some testing result I got |
| Comment by Yuan Fang [ 30/Sep/22 ] |
|
Thank you for reporting this issue. We need additional information to diagnose the problem. Would you please provide:
Regards, Yuan |