What setting is it that when changed would cause this warning to start appearing in logs.
node_Compute1: The open files limit is 10240; raising to 1048575.
A number of different changes were made recently to our grid servers and those changes resulted in the above message showing up in logs where prior to the changes the warning was not present.
I thought the setting was the ulimit -n but that has been put back to the original setting and we are still getting the warning.
I'm not sure off the top of my head but if you modify a job to run "ulimit -a" as a Before Job option, then you could look for which show a current value of 10240. That should at least narrow it down if not answer the question.
-craig
"You can never have too many knives" -- Logan Nine Fingers
We've got the ulimit settings back to where they were before all the changes were applied but something still is causing this message to appear in the logs.
I was quite surprised to still see the msgs in the logs after resetting the ulimit values.
While you have tried your hands on the ulimit setting already... I would like to add few more things on the same.
The user-id which is running the job, user-id which has been used to create the node directories, user-id which is used to make communication possible between the grid architecture---- I hope every user-id has ulimit set to unlimited.
abhinavagarwal wrote:The user-id which is running the job, user-id which has been used to create the node directories, user-id which is used to make communication possible between the grid architecture---- I hope every user-id has ulimit set to unlimited.!
We only changef the ulimit setting on the ids that are used for submitting jobs. How would I determine which other ids are involved?