Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16620
After thinking about this for a few more minutes, I'm going to retract my
earlier statement about preferring my approach to yours. I think we can file a
JIRA for the bigger problem of inconsistent state between the different
components -- but no reason to force this PR to fix that bigger scheduler
issue. Your approach (or the alternative I proposed immediately above)
surgically fix the problem and I think it's good to merge that bug-fix
separately from a more significant re-thinking of the logic here.
---
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
