MaxNoOfOpenFiles NDBD Crash
Posted by:
Adam D
Date: October 17, 2005 07:11PM
8dn, 2sql, 2replica, RHEL4 64bit, 5.0.13rc.
The cluster I have currently was doing next to nothing. Merely running my backup queries on it over night and I come back after a 4 day break and find that one of the 8 datanodes was not connected.
Error log shows this;
Current byte-offset of file-pointer is: 468
Date/Time: Tuesday 18 October 2005 - 03:25:40
Type of error: error
Message: Max number of open files exceeded
Fault ID: 2806
Problem data:
Object of reference: Ndbfs::createAsyncFile
ProgramName: ndbd
ProcessID: 11704
TraceFile: /data/mysql-cluster/ndbd/ndb_17_trace.log.1
Version 5.0.13 (rc)
***EOM***
I have the trace if any mysql guys are interested.
Did some list searching and ulimit -n shows 1024 file limit. Which is a fair amount I would think.
I currently do not have the MaxNoOfOpenFiles parameter set in my mgm config. This seems to default to 40. What should a busy-loaded cluster be set to etc? Are their any drawbacks to this setting.
Subject
Views
Written By
Posted
MaxNoOfOpenFiles NDBD Crash
1934
October 17, 2005 07:11PM
1463
October 18, 2005 03:42PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.