GitHub user aarondav opened a pull request:

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

    [SPARK-3921] Fix CoarseGrainedExecutorBackend's arguments for Standalone 
mode

    The goal of this patch is to fix the swapped arguments in standalone mode, 
which was caused by  
https://github.com/apache/spark/commit/79e45c9323455a51f25ed9acd0edd8682b4bbb88#diff-79391110e9f26657e415aa169a004998R153.
    
    More details can be found in the JIRA: 
[SPARK-3921](https://issues.apache.org/jira/browse/SPARK-3921)
    
    Tested in Standalone mode, but not in Mesos.

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

    $ git pull https://github.com/aarondav/spark fix-standalone

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

    https://github.com/apache/spark/pull/2779.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 #2779
    
----
commit 9d703feb03b3201d73012cb1081b8d20d7ba4ac1
Author: Aaron Davidson <[email protected]>
Date:   2014-10-13T06:26:46Z

    [SPARK-3921] Fix CoarseGrainedExecutorBackend's arguments for Standalone 
mode
    
    The goal of this patch is to fix the swapped arguments in standalone mode, 
which was caused by  
https://github.com/apache/spark/commit/79e45c9323455a51f25ed9acd0edd8682b4bbb88#diff-79391110e9f26657e415aa169a004998R153.
    
    More details can be found in the JIRA: 
[SPARK-3921](https://issues.apache.org/jira/browse/SPARK-3921)
    
    Tested in Standalone mode, but not in Mesos.

----


---
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