Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/14079#discussion_r75700278
--- Diff: docs/configuration.md ---
@@ -1178,6 +1178,80 @@ Apart from these, the following properties are also
available, and may be useful
</td>
</tr>
<tr>
+ <td><code>spark.blacklist.enabled</code></td>
+ <td>
+ <code>true</code> in cluster mode; <br/>
+ <code>false</code> in local mode
+ </td>
+ <td>
+ If set to "true", prevent Spark from scheduling tasks on executors
that have been blacklisted
+ due to too many task failures. The blacklisting algorithm can be
further controlled by the
+ other "spark.blacklist" configuration options.
+ </td>
+</tr>
+<tr>
+ <td><code>spark.blacklist.timeout</code></td>
+ <td>1h</td>
+ <td>
+ (Experimental) How long a node or executor is blacklisted for the
entire application, before it
+ is unconditionally removed from the blacklist to attempt running new
tasks.
+ </td>
+</tr>
+<tr>
+ <td><code>spark.blacklist.task.maxTaskAttemptsPerExecutor</code></td>
+ <td>2</td>
--- End diff --
oops, forgot to update this -- good catch, thanks
---
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
