You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/03/26 12:59:53 UTC
[jira] [Commented] (SPARK-6556) Fix wrong parsing logic of
executorTimeoutMs and checkTimeoutIntervalMs in HeartbeatReceiver
[ https://issues.apache.org/jira/browse/SPARK-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381769#comment-14381769 ]
Apache Spark commented on SPARK-6556:
-------------------------------------
User 'zsxwing' has created a pull request for this issue:
https://github.com/apache/spark/pull/5209
> Fix wrong parsing logic of executorTimeoutMs and checkTimeoutIntervalMs in HeartbeatReceiver
> --------------------------------------------------------------------------------------------
>
> Key: SPARK-6556
> URL: https://issues.apache.org/jira/browse/SPARK-6556
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: Shixiong Zhu
>
> The current reading logic of "executorTimeoutMs" is:
> {code}
> private val executorTimeoutMs = sc.conf.getLong("spark.network.timeout",
> sc.conf.getLong("spark.storage.blockManagerSlaveTimeoutMs", 120)) * 1000
> {code}
> So if "spark.storage.blockManagerSlaveTimeoutMs" is 10000 and "spark.network.timeout" is not set, executorTimeoutMs will be 10000 * 1000. But the correct value should have been 10000.
> "checkTimeoutIntervalMs" has the same issue.
--
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