Skip to content

[SPARK-24566][CORE] spark.storage.blockManagerSlaveTimeoutMs default config #21575

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
xueyumusic wants to merge 5 commits into from
Closed

[SPARK-24566][CORE] spark.storage.blockManagerSlaveTimeoutMs default config #21575

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f594341
blockManagerSlaveTimeoutMs default config
xueyumusic Jun 15, 2018
10c221e
use DurationConvertions
xueyumusic Jun 15, 2018
9673613
add tests
xueyumusic Jun 16, 2018
025bfb3
remove temp val slaveTimeoutMs and timeoutIntervalMs
xueyumusic Jun 21, 2018
536025d
fix format
xueyumusic Jun 29, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,8 @@ private[spark] class HeartbeatReceiver(sc: SparkContext, clock: Clock)
// "spark.network.timeout" uses "seconds", while `spark.storage.blockManagerSlaveTimeoutMs` uses
// "milliseconds"
private val slaveTimeoutMs =
sc.conf.getTimeAsMs("spark.storage.blockManagerSlaveTimeoutMs", "120s")
sc.conf.getTimeAsMs("spark.storage.blockManagerSlaveTimeoutMs",
Copy link
Contributor

@jiangxb1987 jiangxb1987 Jun 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The val slaveTimeoutMs is only used in

spark/core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala

Line 80 in c6ff59a

sc.conf.getTimeAsSeconds("spark.network.timeout", s"${slaveTimeoutMs}ms") * 1000
, so I don't think this change shall fix anything.

Copy link
Contributor

@jiangxb1987 jiangxb1987 Jun 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @zsxwing to confirm.

Copy link
Contributor Author

@xueyumusic xueyumusic Jun 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I look at this carefully, I think your are right, thanks @jiangxb1987 . One case that is not relevant with this PR is like this: set spark.storage.blockManagerSlaveTimeoutMs=900ms and not configure spark.network.timeout, then executorTimeoutMs will be 0 since getTimeAsSeconds loos precision for ms. This config maybe not reasonable. If need fix how about add ensuring > 0 or make executorTimeoutMs's min value as 1, @jiangxb1987 @zsxwing

Copy link
Member

@zsxwing zsxwing Jun 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we never use slaveTimeoutMs. Let's delete this val and just assign this value to executorTimeoutMs.

Copy link
Contributor Author

@xueyumusic xueyumusic Jun 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have removed temp val slaveTimeout, also timeoutIntervalMs is the same case, so removed too, thanks @zsxwing @jiangxb1987

s"${sc.conf.getTimeAsSeconds("spark.network.timeout", "120s") * 1000L}ms")
private val executorTimeoutMs =
sc.conf.getTimeAsSeconds("spark.network.timeout", s"${slaveTimeoutMs}ms") * 1000

Expand Down