[
https://issues.apache.org/jira/browse/MESOS-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926293#comment-13926293
]
Adam B commented on MESOS-969:
------------------------------
I was also seeing the PythonFramework test fail (due to lingering launcher
objects) after the recent containerizer changes. Try a 'make clean' (and
possibly 'make distclean') to clear that out.
When your changes are ready, submit a patch in ReviewBoard and post the link
here.
> resource allocation (memory) beyond availability
> ------------------------------------------------
>
> Key: MESOS-969
> URL: https://issues.apache.org/jira/browse/MESOS-969
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.14.2, 0.18.0
> Reporter: Ashutosh Jain
> Assignee: Ashutosh Jain
> Priority: Minor
>
> I am running my mesos 0.14.2 instance in virtual-box. I had allocated 1466 MB
> of memory to it.
>
> 1. I created the server at 127.0.1.1:5050.
> ./mesos-master.sh
> 2. then I added the system itself as slave and allocated 2000 MB of memory
> using
> ./mesos-slave.sh --master=127.0.1.1:5050 --resources=mem:2000
> and the resources were happily allocated to it.
> (allocated memory was being shown in the GUI at 127.0.1.1:5050 in the browser)
> I even tried with 20000 of memory and still the same results .
> basically it not being checked whether the resources are even available or
> not .
--
This message was sent by Atlassian JIRA
(v6.2#6252)
