[SERVER-43791] Secondary Replica Crushed with error message "... too many open files.." and initial sync also failed with the same error Created: 03/Oct/19  Updated: 03/Oct/19  Resolved: 03/Oct/19

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

Type: Question Priority: Major - P3
Reporter: Miheretu Mamo Assignee: Carl Champain (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongodlog.txt    
Issue Links:
Duplicate
duplicates SERVER-32423 mongod crash Closed
Participants:

 Description   

One of secondary mongod host has crushed recently complaining "..too many open files..." and when we did try to do initial sync it also failed with the same error message.  

This the full information about mongod version and server :

db version v3.4.21
git version: ba2e818de44c9a331ce09a624780a2bd841cf6e4
OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
allocator: tcmalloc
modules: enterprise
build environment:
distmod: rhel70
distarch: x86_64
target_arch: x86_64



 Comments   
Comment by Miheretu Mamo [ 03/Oct/19 ]

Thanks Carl. We will increase open file limits to see if this resolves. I am surprised why the other secondary is not affected given both have the same work load and configuration.

Comment by Carl Champain (Inactive) [ 03/Oct/19 ]

Hi mmamo@costco.com,

Thanks for the report.
Looking at the log you provided, it appears that you've hit the open file limit on your system. You can increase to a larger number of files to avoid hitting this error.

I'm going to close this ticket as a duplicate of SERVER-32423. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group.

Kind regards,
Carl

Generated at Thu Feb 08 05:04:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.