[ 
https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500268#comment-14500268
 ] 

Wangda Tan commented on YARN-3410:
----------------------------------

One question:
What will happen if a running app is removed from state store while RM is 
running, will it cause state corrupted? I think RM will check pid while start 
to avoid this case, correct?

And tried to deploy a local cluster to try this, everything works fine, one 
minor comment about usage:
{code}
Usage: java ResourceManager [-format-state-store] |

   [-remove-application-from-state-store <ApplicationId>]
{code}

Better to format it to?
{code}
Usage: yarn resourcemanager [-format-state-store]
                            [-remove..] <appId>
{code}
                                  

> YARN admin should be able to remove individual application records from 
> RMStateStore
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-3410
>                 URL: https://issues.apache.org/jira/browse/YARN-3410
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager, yarn
>            Reporter: Wangda Tan
>            Assignee: Rohith
>            Priority: Critical
>         Attachments: 0001-YARN-3410-v1.patch, 0001-YARN-3410.patch, 
> 0001-YARN-3410.patch, 0002-YARN-3410.patch, 0003-YARN-3410.patch
>
>
> When RM state store entered an unexpected state, one example is YARN-2340, 
> when an attempt is not in final state but app already completed, RM can never 
> get up unless format RMStateStore.
> I think we should support remove individual application records from 
> RMStateStore to unblock RM admin make choice of either waiting for a fix or 
> format state store.
> In addition, RM should be able to report all fatal errors (which will 
> shutdown RM) when doing app recovery, this can save admin some time to remove 
> apps in bad state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to