Github user ericl commented on the issue:
https://github.com/apache/spark/pull/13152
You wouldn't have to create a new selector after a failure. That case can
be detected by checking if the number of failed replications has increased,
e.g. `if (failedReplications.length > prevNumFails) { reprioritize... }`.
Basically, that state would be tracked in the selector, instead of BlockManager.
I think the main benefit here is that the interface is more flexible as a
developer facing API.
---
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]
