[
https://issues.apache.org/jira/browse/YETUS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16217575#comment-16217575
]
Mike Drob commented on YETUS-561:
---------------------------------
bq. So I'm currently opting to punt on the question and let the current
behavior take precedent
I think the concern is that if you don't set a limit for people, then they
won't set one for themselves either. It's not something that anybody tends to
think about until it's a problem.
If you do set a limit for folks, and they can change it, then I don't think
that makes the OOB experience bad. Java does all sorts of voodoo about setting
heap sizes, and people are happy to ignore them until there's a problem and
then they go in and change things.
> 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)
