aboutsummaryrefslogtreecommitdiff
path: root/docs/running-on-yarn.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/running-on-yarn.md')
-rw-r--r--docs/running-on-yarn.md15
1 files changed, 14 insertions, 1 deletions
diff --git a/docs/running-on-yarn.md b/docs/running-on-yarn.md
index 51c1339165..9d55f435e8 100644
--- a/docs/running-on-yarn.md
+++ b/docs/running-on-yarn.md
@@ -71,9 +71,22 @@ Most of the configs are the same for Spark on YARN as for other deployment modes
</tr>
<tr>
<td><code>spark.yarn.scheduler.heartbeat.interval-ms</code></td>
- <td>5000</td>
+ <td>3000</td>
<td>
The interval in ms in which the Spark application master heartbeats into the YARN ResourceManager.
+ The value is capped at half the value of YARN's configuration for the expiry interval
+ (<code>yarn.am.liveness-monitor.expiry-interval-ms</code>).
+ </td>
+</tr>
+<tr>
+ <td><code>spark.yarn.scheduler.initial-allocation.interval</code></td>
+ <td>200ms</td>
+ <td>
+ The initial interval in which the Spark application master eagerly heartbeats to the YARN ResourceManager
+ when there are pending container allocation requests. It should be no larger than
+ <code>spark.yarn.scheduler.heartbeat.interval-ms</code>. The allocation interval will doubled on
+ successive eager heartbeats if pending containers still exist, until
+ <code>spark.yarn.scheduler.heartbeat.interval-ms</code> is reached.
</td>
</tr>
<tr>