A few corrections to documentation.
Project: http://git-wip-us.apache.org/repos/asf/incubator-spark/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-spark/commit/d3090b79 Tree: http://git-wip-us.apache.org/repos/asf/incubator-spark/tree/d3090b79 Diff: http://git-wip-us.apache.org/repos/asf/incubator-spark/diff/d3090b79 Branch: refs/heads/master Commit: d3090b79a53355828b5315bd5b05c4187468df02 Parents: f4c73df Author: Prashant Sharma <[email protected]> Authored: Thu Dec 12 10:12:06 2013 +0530 Committer: Prashant Sharma <[email protected]> Committed: Thu Dec 12 10:12:06 2013 +0530 ---------------------------------------------------------------------- docs/configuration.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-spark/blob/d3090b79/docs/configuration.md ---------------------------------------------------------------------- diff --git a/docs/configuration.md b/docs/configuration.md index 8cca77e..677d182 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -275,30 +275,30 @@ Apart from these, the following properties are also available, and may be useful </tr> <tr> <td>spark.akka.timeout</td> - <td>60</td> + <td>100</td> <td> Communication timeout between Spark nodes, in seconds. </td> </tr> <tr> <td>spark.akka.heartbeat.pauses</td> - <td>60</td> + <td>600</td> <td> - Acceptable heart beat pause in seconds for akka, tune this if you expect GC pauses or network delays (reconnections) etc. + This is set to a larger value to disable failure detector that comes inbuilt akka. It can be enabled again, if you plan to use this feature (Not recommended). Acceptable heart beat pause in seconds for akka. This can be used to control sensitivity to gc pauses. Tune this in combination of `spark.akka.heartbeat.interval` and `spark.akka.failure-detector.threshold` if you need to. </td> </tr> <tr> <td>spark.akka.failure-detector.threshold</td> - <td>12.0</td> + <td>300.0</td> <td> - Tuning this is not recommended unless you are sure what you are doing. This maps to akka's `akka.remote.transport-failure-detector.threshold`. Usually having a larger value of `spark.akka.pauses` should suffice. + This is set to a larger value to disable failure detector that comes inbuilt akka. It can be enabled again, if you plan to use this feature (Not recommended). This maps to akka's `akka.remote.transport-failure-detector.threshold`. Tune this in combination of `spark.akka.heartbeat.pauses` and `spark.akka.heartbeat.interval` if you need to. </td> </tr> <tr> <td>spark.akka.heartbeat.interval</td> - <td>5</td> + <td>1000</td> <td> - A larger interval value in seconds reduces network overhead and a smaller value might be more informative for akka's failure detector. Tune this in combination of `spark.akka.heartbeat.pauses` and `spark.akka.failure-detector.threshold` if you need to. + This is set to a larger value to disable failure detector that comes inbuilt akka. It can be enabled again, if you plan to use this feature (Not recommended). A larger interval value in seconds reduces network overhead and a smaller value ( ~ 1 s) might be more informative for akka's failure detector. Tune this in combination of `spark.akka.heartbeat.pauses` and `spark.akka.failure-detector.threshold` if you need to. Only positive use case for using failure detector can be, a sensistive failure detector can help evict rogue executors really quick. However this is usually not the case as gc pauses and network lags are expected in a real spark cluster. Apart from that enabling this leads to a lot of exchanges of heart beats between nodes leading to flooding the network with those. </td> </tr> <tr>
