Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18874
I think the current fix is a feasible and simple solution for the scenarios
mentioned above. As far as I understand from the comments above, ideally this
problem should not be happened, but in a real cluster especially driver is
stuck by GC or others, this will be happened easily and delay the task
scheduling, to the extreme going into deadlock situation.
My only concern is that will this fix bring in some edge cases due to the
complexity of this part (though I cannot imagine it currently). Since now idle
executors will stay in the `executorsPendingToRemove` queue indefinitely.
---
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
