On Tue, Mar 20, 2018 at 11:08:02AM +0100, Sms Backup wrote:
> Dear all,
> We have in our configuration multiple servers assigned to multiple queues.
> To limit slots number per system, I tried to create qouta:
> {
> name slots
> description Limit slots usage per node to number of cores
> enabled FALSE
> limit queues !interactive.q hosts {@allhosts} to slots=40
> }
> Expected result was to limit slots usage per host to 40 for
> non-interactive queus, but allow interactive jobs even if all slots are
> taken.
> It is doing it's job, but enabling this quota causes hundreds of thousands
> messages from SGE master to be passed to systemd-journalctl, causing
> systemd-journalctl eat 100% CPU, and make SGE master almost not usable,
> example:> Did anyone had similar issue ? Any other ideas how to limit slots usage, > and not causing this kind of issue ? Or maybe it is possible to force SGE > not to send so many messages to systemd-journald ? > Regards, > Jakub If you only have one non-interactive queue you could just set the number of slots for that queue on each host. It would probably be useful to see what messages grid engine is sending to journald. Hopefully it has retained a few sample messages rather than suppressing them all. A look at your sge_conf and sched_conf might give a clue as to what is generating the messages. William
signature.asc
Description: PGP signature
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
