Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17620
@jiangxb1987 according to what @lvdongr described, seems there's an issue
in state transition for recovered master:
> This happend at the time the previous master leader remove the died
worker ,clear the worker's node on persistEngine(we use zookeeper),But before
the worker node was removed from the zookeeper ,the leader changed. The new
master leader recovery from the zookeeper ,and read the died worker node. Then
the new leader find the worker died and trying to remove it ,and try to clear
the node on zookeeper,but the node has been removed by the previous leader ,so
an exception was throw, and the recovery fail. Then the leader will always in
COMPLETING_RECOVERY state,and all the application registered cannot get
resources .
Based on the description, it looks like a contention issue, but here the
fix is just simply a `try catch` solution. IMHO we'd better fix the root cause
if we want to move forward this issue.
---
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]
