infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15685) Raise UserTasksMax in systemd
Date Mon, 01 Jan 2018 06:11:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307374#comment-16307374
] 

Allen Wittenauer commented on INFRA-15685:
------------------------------------------

Ok, this change has allowed me to pump up the number of processes tremendously.  Thanks.

The offline problem is completely related.  Basically, the # of processes and Java native
threads are limited by the UserTasksMax number.  As soon as that number is hit, any new processes/threads
will die with out of memory.  In the case of Jenkins, it causes the node to go offline.  Jenkins
needs to have much better cgroup support or the ability to run jobs as users different than
the slave process in order to prevent this problem from  happening

> Raise UserTasksMax in systemd
> -----------------------------
>
>                 Key: INFRA-15685
>                 URL: https://issues.apache.org/jira/browse/INFRA-15685
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Allen Wittenauer
>            Assignee: Daniel Takamori
>            Priority: Critical
>              Labels: pull-request-available
>
> systemd limits the maximum number of processes (and native Java threads) a user may consume
on a box via UserTasksMax.  This should probably be raised in the case of Jenkins build hosts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message