Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1360#issuecomment-53101677
Will blacklisting executors with appropriate value not solve this ? (If
executor is still usable, but some tasks fail on the specific executor for
whatever reason).
The more general problem of detecting straddlers and/or "misbehaving"
executors is something we have yet to do in spark.
On 22-Aug-2014 11:10 pm, "Apache Spark QA" <[email protected]> wrote:
> QA tests have finished
>
<https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19085/consoleFull>
> for PR 1360 at commit 206a448
>
<https://github.com/apache/spark/commit/206a44853edf5caea9ce2d8ae83af3d999f5cf41>
> .
>
> - This patch *passes* unit tests.
> - This patch merges cleanly.
> - This patch adds no public classes.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/1360#issuecomment-53094602>.
>
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
