Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7716#issuecomment-128847557
I guess one way to reproduce this would be to call `sc.killExecutor("1")`
twice. Since it's the same executor both times, we may double count the number
of executors to remove, which could result in the `-1` thing you saw.
However, I believe this problem already existed in 1.4 well before
SPARK-8119 and related changes. The old code didn't guard against that either:
https://github.com/apache/spark/blob/4b5bbc589e11d882c993a3e6daeb0cdad9789e76/core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala#L391.
---
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]
