GitHub user dragos opened a pull request:

    https://github.com/apache/spark/pull/4984

    [MESOS][SPARK-6287] Add dynamic allocation to the coarse-grained Mesos 
scheduler

    This is largely based on extracting the dynamic allocation parts from 
@tnachen's #3861.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dragos/spark 
issue/mesos-coarse-dynamicAllocation

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/4984.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4984
    
----
commit 6a259fcb951cba0b305a57dfc3168e69cf1658ba
Author: Iulian Dragos <[email protected]>
Date:   2015-03-10T20:20:58Z

    Add dynamic allocation to the Spark coarse-grained scheduler.
    
    Based on #3861.

commit 01709d5c55508b9e0fb46202b6325244499dc0a6
Author: Dean Wampler <[email protected]>
Date:   2015-03-11T00:08:33Z

    First unit test for CoarseMesosSchedulerBackend.

commit 1f5c33904bf3d376e9515ce486fae920b7040966
Author: Iulian Dragos <[email protected]>
Date:   2015-03-11T04:56:42Z

    Properly decline offer.

commit 0954a75eeba49320b45452baa2cdb2e2d52a1611
Author: Iulian Dragos <[email protected]>
Date:   2015-03-11T04:57:02Z

    Added a second test and properly verified the first one.

commit 129dc3605ecfc6e59e66e1392dbf8e4110718b39
Author: Iulian Dragos <[email protected]>
Date:   2015-03-11T17:18:46Z

    Refactored duplicated code.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to