[jira] [Commented] (SPARK-27677) Disk-persisted RDD blocks served by shuffle service, and ignored for Dynamic Allocation
[ https://issues.apache.org/jira/browse/SPARK-27677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837868#comment-16837868 ] Apache Spark commented on SPARK-27677: -- User 'attilapiros' has created a pull request for this issue: https://github.com/apache/spark/pull/24499 > Disk-persisted RDD blocks served by shuffle service, and ignored for Dynamic > Allocation > --- > > Key: SPARK-27677 > URL: https://issues.apache.org/jira/browse/SPARK-27677 > Project: Spark > Issue Type: New Feature > Components: Block Manager, Spark Core >Affects Versions: 2.4.3 >Reporter: Imran Rashid >Priority: Major > > Disk-cached RDD blocks are currently unavailable after an executor is > removed. However, when there is an external shuffle service, the data > remains available on disk and could be served by the shuffle service. This > would allow dynamic allocation to reclaim executors with only disk-cached > blocks more rapidly, but still keep the cached data available. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-27677) Disk-persisted RDD blocks served by shuffle service, and ignored for Dynamic Allocation
[ https://issues.apache.org/jira/browse/SPARK-27677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837869#comment-16837869 ] Apache Spark commented on SPARK-27677: -- User 'attilapiros' has created a pull request for this issue: https://github.com/apache/spark/pull/24499 > Disk-persisted RDD blocks served by shuffle service, and ignored for Dynamic > Allocation > --- > > Key: SPARK-27677 > URL: https://issues.apache.org/jira/browse/SPARK-27677 > Project: Spark > Issue Type: New Feature > Components: Block Manager, Spark Core >Affects Versions: 2.4.3 >Reporter: Imran Rashid >Priority: Major > > Disk-cached RDD blocks are currently unavailable after an executor is > removed. However, when there is an external shuffle service, the data > remains available on disk and could be served by the shuffle service. This > would allow dynamic allocation to reclaim executors with only disk-cached > blocks more rapidly, but still keep the cached data available. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-27677) Disk-persisted RDD blocks served by shuffle service, and ignored for Dynamic Allocation
[ https://issues.apache.org/jira/browse/SPARK-27677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837629#comment-16837629 ] Imran Rashid commented on SPARK-27677: -- I'm breaking this out of SPARK-25888. [~attilapiros] is already working on a fix for this, the current pr is https://github.com/apache/spark/pull/24499 > Disk-persisted RDD blocks served by shuffle service, and ignored for Dynamic > Allocation > --- > > Key: SPARK-27677 > URL: https://issues.apache.org/jira/browse/SPARK-27677 > Project: Spark > Issue Type: New Feature > Components: Block Manager, Spark Core >Affects Versions: 2.4.3 >Reporter: Imran Rashid >Priority: Major > > Disk-cached RDD blocks are currently unavailable after an executor is > removed. However, when there is an external shuffle service, the data > remains available on disk and could be served by the shuffle service. This > would allow dynamic allocation to reclaim executors with only disk-cached > blocks more rapidly, but still keep the cached data available. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
