What I'm saying is even putting them within the upstart script, per the Mesos documentation, isn't working for the file block limit. We're still getting 8MB useable, and as a result executors fail when attempting to write larger files.
Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Mon, Apr 25, 2016 at 11:53 AM, haosdent <[email protected]> wrote: > If you set in your upstart script, it isn't system wide and only effective > in that session. I think need change /etc/security/limits.conf > and /etc/sysctl.conf to make your ulimit work globally. > > On Tue, Apr 26, 2016 at 12:43 AM, June Taylor <[email protected]> wrote: > >> Somewhere an 8MB maximum file size is being applied on just one of our >> slaves, for example. >> >> >> Thanks, >> June Taylor >> System Administrator, Minnesota Population Center >> University of Minnesota >> >> On Mon, Apr 25, 2016 at 11:42 AM, June Taylor <[email protected]> wrote: >> >>> We are operating a 6-node cluster running on Ubuntu, and have noticed >>> that the ulimit settings within the slave context are difficult to set and >>> predict. >>> >>> The documentation is a bit unclear on this point, as well. >>> >>> We have had some luck adding a configuration line to >>> /etc/init/mesos-slave.conf as follows: >>> limit nofile 20000 20000 >>> limit fsize unlimited unlimited >>> >>> The nofile limit seems to be respected, however the fsize limit does not. >>> >>> It is also mysterious that the system-wide limits are not inherited by >>> the slave process. We would prefer to set all of these system-wide and have >>> mesos-slave observe them. >>> >>> Can you please advise where you are setting your ulimits for the >>> mesos-slave if it is working for you? >>> >>> Thanks, >>> June Taylor >>> System Administrator, Minnesota Population Center >>> University of Minnesota >>> >> >> > > > -- > Best Regards, > Haosdent Huang >

