[
https://issues.apache.org/jira/browse/AURORA-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474272#comment-15474272
]
Maxim Khutornenko commented on AURORA-1766:
-------------------------------------------
I don't think removing the overhead is a viable option. While CPU as a
compressible resource can likely be absorbed by tasks with little to no impact,
the lack of RAM may create hard to troubleshoot user scenarios. Telling our
users to allocate "N MB of extra RAM" for every task may not scale when/if we
decide to change it in either direction.
> Account for thermos executor overhead in reported CPU usage to user
> -------------------------------------------------------------------
>
> Key: AURORA-1766
> URL: https://issues.apache.org/jira/browse/AURORA-1766
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Rick Mangi
>
> The default .25 CPU overhead taken for thermos can be hugely impactful on
> clusters with many tasks and it's not reported to the user in the web UI.
> Ideally the resources used by the cluster should be reported accurately. We
> ran into a case where we could not launch jobs even though we thought we had
> plenty of free cores.
> Alternatively, the thermos overhead could be removed completely. I think it's
> confusing personally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
