[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    Re: [uWSGI] vassal config: set per-worker cgroups?
From:       Roberto De Ioris <roberto () unbit ! it>
Date:       2017-02-22 7:41:23
Message-ID: 1fcc79c57f37f63480ef336aa328e635.squirrel () squirrelmail ! unbit ! it
[Download RAW message or body]


> Hi there,
>
> If I may can resuscitate a very old thread, I think we might still be
> interested in per-worker cgroup settings, something like
>
> cgroup =
> /sys/fs/cgroups/memory/domains/vassal-domain-name/worker-$WORKER_ID
>
>
> We can't run the master as root, but can run the emperor as root.  We're
> using various other cgroups already, so it'd just be a matter of setting
> a unique name per worker to the cgroup, from within the vassal config
> file -- is there any way to do that?
>
>
> evil-reload-on-as *might* work, but the advantage of the cgroup is the
> user will actually see a MemoryError exception, rather than just a
> random "killed".  I think...
>
>

Hi Harry, unfortunately i see no easy solution (unless you want each
master to constantly inform the emperor about workers to move into
cgroups).

What about improving the error message of the evil reload (but i suggest
you to use evil-reload-on-rss so you will monitory real emory) ?

-- 
Roberto De Ioris
http://unbit.com
_______________________________________________
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

[prev in list] [next in list] [prev in thread] [next in thread]