aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1021) Increase MIN_THERMOS_RESOURCES to prevent thermos OOMs.
Date Tue, 20 Jan 2015 19:22:35 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284250#comment-14284250
] 

Zameer Manji commented on AURORA-1021:
--------------------------------------

[~StephanErb]: If the user specifies a very small value (say 1MB) and we create a container
with 1MB of RAM, it is possible for the container to OOM when the executor is creating the
sandbox. This results in no sandbox created and can make this issue difficult to debug. This
is here to ensure that the smallest container created by Aurora doesn't have the executor
OOM right away. This ensures the sandbox is created and the user can look at their application
logs and make the decision to resize the container.

> Increase MIN_THERMOS_RESOURCES to prevent thermos OOMs.
> -------------------------------------------------------
>
>                 Key: AURORA-1021
>                 URL: https://issues.apache.org/jira/browse/AURORA-1021
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Zameer Manji
>            Assignee: Zameer Manji
>            Priority: Minor
>
> After doing some experiments that involved reducing the executor overhead to 0 I noticed
the peak executor memory usage is greater than 128MB. This causes OOMs when the container
starts even for very small tasks. To prevent this the memory portion of MIN_THERMOS_RESORUCES
should be increased to 256MB.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message