Github user lvdongr commented on the issue:

    https://github.com/apache/spark/pull/17620
  
    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 .
    
    
![failfetchresource](https://cloud.githubusercontent.com/assets/25652150/25209181/f7e31528-25ab-11e7-9eb2-e2f15db2dcac.png)



---
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

Reply via email to