You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2015/01/17 09:33:34 UTC

[jira] [Commented] (AURORA-1021) Increase MIN_THERMOS_RESOURCES to prevent thermos OOMs.

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

Stephan Erb commented on AURORA-1021:
-------------------------------------

Excuse my ignorance: What is the point of configurable thermos resources? If thermos can reach its peak memory usage at any given time, I always have to size the cgroup for peak thermos + peak memory of my task.

> 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)