Github user kayousterhout commented on a diff in the pull request: https://github.com/apache/spark/pull/14079#discussion_r92103358 --- Diff: docs/configuration.md --- @@ -1339,6 +1347,28 @@ Apart from these, the following properties are also available, and may be useful </td> </tr> <tr> + <td><code>spark.blacklist.application.maxFailedTasksPerExecutor</code></td> + <td>2</td> + <td> + (Experimental) How many different tasks must fail on one executor, in successful task sets, + before the executor is blacklisted for the entire application. Blacklisted executors will + be automatically added back to the pool of available resources after the timeout specified by + <code>spark.blacklist.timeout</code>. Note that with dynamic allocation, though, the executors + may get marked as idle and be reclaimed by the cluster manager. + </td> +</tr> +<tr> + <td><code>spark.blacklist.application.maxFailedExecutorsPerNode</code></td> + <td>2</td> + <td> + (Experimental) How many different executors must be blacklisted for the entire application, + before the node is blacklisted for the entire application. Blacklisted nodes will + be automatically added back to the pool of available resources after the timeout specified by + <code>spark.blacklist.timeout</code>. Note that with dynamic allocation, though, the executors + may get marked as idle and be reclaimed by the cluster manager. --- End diff -- the executors on the node may
--- 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. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org