[
https://issues.apache.org/jira/browse/YETUS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-561:
-----------------------------------
Attachment: YETUS-561.03.patch
Doh. Good catch.
-03:
* fix the usage output error
* switch to += for array appends in this part of the universe
At this point, I don't think we can prevent the system crash that Hadoop is
causing with this patch. I think that problem is something much bigger than
just a simple OOM. That said, this patch does help in those OOM situations,
first by giving a quantifiable amount of memory that is expected to be used and
second by mostly guaranteeing that Yetus spawned processes die first rather
than more important processes (e.g., init/systemd).
> 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, YETUS-561.01.patch,
> YETUS-561.02.patch, YETUS-561.03.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)
