[
https://issues.apache.org/jira/browse/YETUS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217470#comment-16217470
]
Allen Wittenauer commented on YETUS-561:
----------------------------------------
This is something I haven't played with before. After some brief testing, I
suspect that docker's -m param works differently depending upon kernel
configuration. In my tests, this only killed individual processes inside the
container and not the entire container. That's both good and bad. I'm still
doing a more full scale test, but since we're killing individual commands,
Yetus *should* return a -1 vote on those tests.
> 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)
