You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Ashutosh Jain (JIRA)" <ji...@apache.org> on 2014/03/18 20:02:48 UTC

[jira] [Comment Edited] (MESOS-969) resource allocation (memory) beyond availability

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

Ashutosh Jain edited comment on MESOS-969 at 3/18/14 7:02 PM:
--------------------------------------------------------------

submitting the patch to review board. take a look
link to review : https://reviews.apache.org/r/19263/


was (Author: a9393j):
submitting the patch to review board. take a look

> 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
>         Attachments: mesos-969.patch
>
>
> 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)