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 Tue, 02 Jan 2018 16:45:00 GMT

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

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

bq.  I don't think allowing multiple users (and multiple x UserTasksMax/ulimit etc) is the
answer

You only need two users.  One to run the Jenkins slave process and one to run the test job.
 There's no need to make more than that. UserTasksMax can remain one setting since I'm sure
pid max was raised (right??) and the Jenkins slave process won't need that many.  There are
other answers though (e.g, direct cgroup manipulation) but all of them require code changes
to Jenkins.

Until that happens, errant jobs that don't enforce their own limits will always be able to
bring down the Jenkins build node. 

> 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