Lars Albertsson
unread,Apr 6, 2016, 10:15:23 AM4/6/16Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Arash Rouhani Kalleh, eri...@gogotech.hk, Luigi, Michal Szczecinski
Luigi does have a primitive for resource overload protection, but at a
global level, i.e. enforced by the central scheduler. The
documentation is well hidden:
http://luigi.readthedocs.org/en/stable/configuration.html#resources
Are you running multiple Luigi workers, and would like to avoid the
sum of resources required to overload the machine? In that case, it
might make sense to port the resource logic from the central scheduler
to the worker side. It would probably be a straightforward
implementation, and would be useful as simple overload protection,
e.g. on a farm of worker machines. It would be less powerful, but
simpler than running frameworks like Mesos.
If you are only concerned with preventing a single job from consuming
too much resources, just run it in a container, e.g. with ulimit or
Docker.
Regards,
Lars Albertsson
Data engineering consultant
www.mapflat.com
+46 70 7687109