Re: Too many files

2016-12-30 Thread Kiril Menshikov
I found problems in systemd/linux. First, I use wildcard in limit.conf which I changed to specific user. Second, in service I define user and group to. Because before even ulimit -n show correct value and process was launched with correct user. Actual process limit was default. Thanks, -Kiril

Re: Too many files

2016-12-30 Thread June Taylor
Kiril, We had this problem too and had a confusing time understanding how the ulimit setting was being applied to mesos executors. Here is what we learned which seems to work: The startup script /usr/bin/mesos-init-wrapper reads configuration values from /etc/default/mesos In this file, the

Re: Too many files

2016-12-29 Thread haosdent
No. It means executor/task only could open 4000 files exclude child processes. On Fri, Dec 30, 2016 at 2:32 AM, Kiril Menshikov wrote: > It’s 4000. Does this mean that sum of all child open files should not > exceed this value? Because I see that task limit is also 4000. >

Re: Too many files

2016-12-29 Thread Kiril Menshikov
It’s 4000. Does this mean that sum of all child open files should not exceed this value? Because I see that task limit is also 4000. > On Dec 29, 2016, at 19:48, haosdent wrote: > > Hi, @Kiril It sounds like your executor reaches max open file limit. May you > show the

Re: Too many files

2016-12-29 Thread haosdent
Hi, @Kiril It sounds like your executor reaches max open file limit. May you show the result of $ cat /proc/${your_executor_pid}/limits On Fri, Dec 30, 2016 at 1:07 AM, Kiril Menshikov wrote: > ​Hi, > > I have executor which run java programs. One executor execute

Too many files

2016-12-29 Thread Kiril Menshikov
​Hi, I have executor which run java programs. One executor execute around 800 tasks. Last ~100 failed with "Too many open files". I increased nofile and nproc limits. During my debug I could not say that problem in in the tasks. But some times linux reach limits. I see some boxes are good with