Github user sryza commented on a diff in the pull request:

    https://github.com/apache/spark/pull/119#discussion_r10506244
  
    --- Diff: docs/configuration.md ---
    @@ -375,7 +376,7 @@ Apart from these, the following properties are also 
available, and may be useful
       <td>spark.akka.heartbeat.interval</td>
       <td>1000</td>
       <td>
    -    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. 
    +    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.
    --- End diff --
    
    False change?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to