[
https://issues.apache.org/jira/browse/SPARK-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shixiong Zhu updated SPARK-6556:
--------------------------------
Description:
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.
was:
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, executorTimeoutMs
will be 10000 * 1000. But the correct value should have been 10000.
"checkTimeoutIntervalMs" has the same issue.
> 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: [email protected]
For additional commands, e-mail: [email protected]
