aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala1
-rw-r--r--docs/configuration.md3
2 files changed, 3 insertions, 1 deletions
diff --git a/core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala b/core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala
index c3764ac671..5242ab6f55 100644
--- a/core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala
+++ b/core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala
@@ -32,6 +32,7 @@ import org.apache.spark.util._
* A heartbeat from executors to the driver. This is a shared message used by several internal
* components to convey liveness or execution information for in-progress tasks. It will also
* expire the hosts that have not heartbeated for more than spark.network.timeout.
+ * spark.executor.heartbeatInterval should be significantly less than spark.network.timeout.
*/
private[spark] case class Heartbeat(
executorId: String,
diff --git a/docs/configuration.md b/docs/configuration.md
index ebd0aa796d..8aea74505e 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -987,7 +987,8 @@ Apart from these, the following properties are also available, and may be useful
<td>10s</td>
<td>Interval between each executor's heartbeats to the driver. Heartbeats let
the driver know that the executor is still alive and update it with metrics for in-progress
- tasks.</td>
+ tasks. spark.executor.heartbeatInterval should be significantly less than
+ spark.network.timeout</td>
</tr>
<tr>
<td><code>spark.files.fetchTimeout</code></td>