[
https://issues.apache.org/jira/browse/YETUS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217541#comment-16217541
]
Allen Wittenauer commented on YETUS-561:
----------------------------------------
One other point:
I'm opting to set the hard limit and the not soft one. The soft one only kicks
in when Docker "senses" low RAM (insert picture of Deanna Troi here). Given
how overcommit works and the speed at which things can go to "great! -> bad!"
on the Linux kernel, I'm not convinced that the soft limit is the one to use.
(Also, see [~busbey]'s comment about "fast enough")
> 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)
