[
https://issues.apache.org/jira/browse/YETUS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217630#comment-16217630
]
Marco Zühlke commented on YETUS-561:
------------------------------------
bq. Note to myself and future readers:
http://matthewkwilliams.com/index.php/2016/03/17/docker-cgroups-memory-constraints-and-java-cautionary-tale/
is particularly interesting.
In the last comment, Charlie Hunt mentions a feature available in newer Java
versions (starting with Java SE 8u131). [Java SE support for Docker CPU and
memory
limits|https://blogs.oracle.com/java-platform-group/java-se-support-for-docker-cpu-and-memory-limits]
Second fact, unknown to me before: Specify {{memory}}, but no {{memory-swap}} —
the container ram is limited and it may use an equivalent amount of swap as
memory.
> Ability to limit Docker container's RAM usage
> ---------------------------------------------
>
> Key: YETUS-561
> URL: https://issues.apache.org/jira/browse/YETUS-561
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Affects Versions: 0.6.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Critical
> Attachments: YETUS-561.00.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
