GitHub user andrewor14 opened a pull request:

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

    [SPARK-4140] Document dynamic allocation

    Once the external shuffle service is also documented, the dynamic 
allocation section will link to it. Let me know if the whole dynamic allocation 
should be moved to its separate page; I personally think the organization might 
be cleaner that way.
    
    This patch builds on top of @oza's work in #3689.
    
    @aarondav @pwendell

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

    $ git pull https://github.com/andrewor14/spark document-dynamic-allocation

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

    https://github.com/apache/spark/pull/3731.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 #3731
    
----
commit 53cff5840923af81e048c0333117dc48163e4408
Author: Tsuyoshi Ozawa <[email protected]>
Date:   2014-12-13T07:34:25Z

    Adding a documentation about dynamic resource allocation.
    
    Signed-off-by: Tsuyoshi Ozawa <[email protected]>

commit 6827b56e37e25d64ce52af1caad742563c2bdb40
Author: Tsuyoshi Ozawa <[email protected]>
Date:   2014-12-16T17:14:15Z

    Fixing a documentation of spark.dynamicAllocation.enabled.
    
    Signed-off-by: Tsuyoshi Ozawa <[email protected]>

commit 8c64004029ece1700fb5930ba1e9ddc19c1c3bd1
Author: Andrew Or <[email protected]>
Date:   2014-12-18T06:35:38Z

    Add documentation for dynamic allocation (without configs)

commit 246fb44a6f508178a8730d4c3095237bb66cfc33
Author: Andrew Or <[email protected]>
Date:   2014-12-18T06:36:30Z

    Merge branch 'SPARK-4839' of github.com:oza/spark into 
document-dynamic-allocation

commit b9843f2c673f30c5111f2a2a29e15dcde00042db
Author: Andrew Or <[email protected]>
Date:   2014-12-18T06:50:25Z

    Document the configs as well

----


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