[
https://issues.apache.org/jira/browse/AURORA-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238130#comment-15238130
]
zane silver commented on AURORA-1662:
-------------------------------------
I believe the latest supported version of Aurora is compatible with Mesos
0.25.0. Has it been verified that Aurora 0.12.0 is compatible with Mesos 0.26.0?
Additionally, what's the earliest version of Mesos that supports the
"--isolation" flag?
> No Memory and CPU Enforcement
> -----------------------------
>
> Key: AURORA-1662
> URL: https://issues.apache.org/jira/browse/AURORA-1662
> Project: Aurora
> Issue Type: Bug
> Components: Executor
> Affects Versions: 0.11.0
> Reporter: zane silver
>
> I'm running a job that is consuming more memory (ram) than I've been
> allocated. The Mesos and Aurora UIs properly display the memory utilization
> vs the allocated/requested amount. However, the executor is not stopped once
> the job extends beyond it's limit. There appears to be no enforcement.
> Looking at the source, it also seems that there is only enforcement on the
> disk usage. I see in
> (src/main/python/apache/aurora/executor/common/resource_manager.py) the
> ResourceManager status() method, that only disk is explicitly checked.
> I feel like I must be missing something and that the enforcement for cpu and
> memory is actually elsewhere. If not, this is an easy fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
