GitHub user lvdongr opened a pull request:

    https://github.com/apache/spark/pull/17620

    [SPARK-20305][Spark Core]Master may keep in the state of "COMPELETING…

    ## What changes were proposed in this pull request?
    Master may keep in the state of "COMPELETING_RECOVERY",then all the 
application registered cannot get resources, when the leader master change.
    This happend when a exception was thrown during the Master trying to 
recovery(completeRecovery method in the master.scala  ). Then the leader will 
always in COMPLETING_RECOVERY state ,for the leader can only change to alive 
from state of RecoveryState.RECOVERING.
    
    ## How was this patch tested?
    manual tests
    
    Please review http://spark.apache.org/contributing.html before opening a 
pull request.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lvdongr/spark SPARK20305

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/17620.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17620
    
----
commit 44b9415dd1c6ac854a9debddd67c9dcb00e8df69
Author: lvdongr <lv.dongd...@zte.com.cn>
Date:   2017-04-12T07:34:03Z

    [SPARK-20305][Spark Core]Master may keep in the state of 
"COMPELETING_RECOVERY",then all the application registered cannot get 
resources, when the leader master change. has been successfully created.

----


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