[YETUS-561] Ability to limit user process counts and Docker container's RAM usage

• Type: New Feature
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.7.0
• Component/s: Precommit

Release Note

<!-- markdown -->
Apache Yetus now enforces some basic controls around resource limits.

* `--proclimit` sets `ulimit -Sh` for an upper bound on the amount of processes and Java native threads that may be spawned. The default is set to 1000.

* Docker `--memory` sizes are now sized with the `--dockermemlimit` option. By default, 4 gigabytes are allocated.

* Docker mode will set the OOM adjustment value for any process within the container to 500. This is to help guide the kernel to kill Apache Yetus spawned processes before potentially killing any others in low memory conditions. This is to prevent the death of, for example, the Jenkins agent.

If any process attempts to violate those controls over those limits, there is a very high chance that any process spawned by Apache Yetus and Apache Yetus itself will be killed.

• Flags: Important
• Assignee: Allen Wittenauer
• Reporter: Allen Wittenauer
• Created: 24/Oct/17 15:15
• Updated: 17/Jan/18 16:12
• Resolved: 28/Oct/17 12:43

Description

Hadoop is blowing up nodes due to unit tests that consume all of RAM. In an attempt to keep nodes alive, Yetus needs the ability to put an upper limit on the amount that a Docker container can use.

Issue Links

• is required by: YETUS-570 Report and optionally kill stale JVMs between unit test modules
• relates to: INFRA-15373 Various Jenkins bits are in trouble
• relates to: HDFS-12711 deadly hdfs test