Github user davies commented on the pull request:
https://github.com/apache/spark/pull/3541#issuecomment-65312874
@mridulm In the case of one executor restarted on failure, the executor id
will be changed, put the previous executor-id in blacklist does make sense. It
only help when task failed on the particular status of a executor (such as OOM,
too many open files). In this cases, host based blacklist also could help.
One situation that executor-id based blacklist will better than host based
is that you have only one host and several executors on it. In this case, you
will see some delay of scheduling once task failed. Also, executor-id based
blacklist may improve data locality if reschedule the failed task into same
host, the performance gain should be small, because the percentage of failed
tasks should be small.
It's more common that user will have multiple hosts than multiple executors
on single host, and host based blacklist can help in most of failure cases, it
should be turned on by default. It will be good to have host based blacklist
together with executor-id based, but it will complicated the code a lot, do the
benefits in above worth it?
---
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]
