You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Iulian Dragos (JIRA)" <ji...@apache.org> on 2015/05/19 15:59:00 UTC

[jira] [Commented] (SPARK-872) Should revive offer after tasks finish in Mesos fine-grained mode

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

Iulian Dragos commented on SPARK-872:
-------------------------------------

I think we should close this due to inactivity. What is the policy w.r.t. to the status to use?

> Should revive offer after tasks finish in Mesos fine-grained mode 
> ------------------------------------------------------------------
>
>                 Key: SPARK-872
>                 URL: https://issues.apache.org/jira/browse/SPARK-872
>             Project: Spark
>          Issue Type: Improvement
>          Components: Mesos
>    Affects Versions: 0.8.0
>            Reporter: xiajunluan
>
> when running spark on latest Mesos release, I notice that spark on mesos fine-grained could not schedule spark tasks effectively, for example, if slave has 4 cpu cores resource, mesos master will call resourceOffer function of spark until 4 cpu cores are all free. but In my points like standalone scheduler mode, if one task finished and one cpus core is free, Mesos master should call spark resourceOffer to allocate resource to tasks. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org