[jira] [Commented] (SPARK-9795) Dynamic allocation: avoid double counting when killing same executor twice
[ https://issues.apache.org/jira/browse/SPARK-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693773#comment-14693773 ] Andrew Or commented on SPARK-9795: -- Looks like this did resolve SPARK-9745. Closing that one as well. > Dynamic allocation: avoid double counting when killing same executor twice > -- > > Key: SPARK-9795 > URL: https://issues.apache.org/jira/browse/SPARK-9795 > Project: Spark > Issue Type: Bug > Components: Spark Core >Affects Versions: 1.4.0 >Reporter: Andrew Or >Assignee: Andrew Or >Priority: Critical > Fix For: 1.5.0 > > > Currently, if we kill the same executor twice in rapid succession, we will > lower the executor target by 2 instead of 1. In cases where we don't > re-adjust the target upwards frequently, this will result in jobs hanging. > This may or may not be the same as SPARK-9745. Until we can verify the > correlation, however, this will remain a separate issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-9795) Dynamic allocation: avoid double counting when killing same executor
[ https://issues.apache.org/jira/browse/SPARK-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680738#comment-14680738 ] Apache Spark commented on SPARK-9795: - User 'andrewor14' has created a pull request for this issue: https://github.com/apache/spark/pull/8078 > Dynamic allocation: avoid double counting when killing same executor > > > Key: SPARK-9795 > URL: https://issues.apache.org/jira/browse/SPARK-9795 > Project: Spark > Issue Type: Bug > Components: Spark Core >Affects Versions: 1.4.0 >Reporter: Andrew Or >Assignee: Andrew Or >Priority: Critical > > Currently, if we kill the same executor twice in rapid succession, we will > lower the executor target by 2 instead of 1. In cases where we don't > re-adjust the target upwards frequently, this will result in jobs hanging. > This may or may not be the same as SPARK-9745. Until we can verify the > correlation, however, this will remain a separate issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
