You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/01/18 21:32:40 UTC

[jira] [Updated] (SPARK-12883) 1.6 Dynamic allocation doc still refers to 1.2

     [ https://issues.apache.org/jira/browse/SPARK-12883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated SPARK-12883:
------------------------------
    Priority: Trivial  (was: Minor)

[~manojsamel] this isn't really worth a JIRA if it's that trivial a change, and you open a pull request to go along with this. That said, I'm not sure this doc is wrong. It's making statements about things true as of 1.2. It might be improved by an update but I'm not sure that's what you're suggesting.

> 1.6 Dynamic allocation doc still refers to 1.2
> ----------------------------------------------
>
>                 Key: SPARK-12883
>                 URL: https://issues.apache.org/jira/browse/SPARK-12883
>             Project: Spark
>          Issue Type: Documentation
>          Components: Documentation
>    Affects Versions: 1.6.0
>            Reporter: Manoj Samel
>            Priority: Trivial
>
> Spark 1.6 dynamic allocation documentation still refers to 1.2. 
> See text "There is currently not yet a solution for this in Spark 1.2. In future releases, the cached data may be preserved through an off-heap storage similar in spirit to how shuffle files are preserved through the external shuffle service"
> It appears 1.6 has parameter to address cache executor spark.dynamicAllocation.cachedExecutorIdleTimeout with default value as infinity.
> Pl update 1.6 documentation to refer to latest release and features



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