[
https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504150#comment-14504150
]
Brahma Reddy Battula commented on YARN-3410:
--------------------------------------------
004-Patch overall LGTM,, One minor comment..[~rohithsharma] can you please
update the following usage also as [~leftnoteasy] also pointed earlier...
{code}
+ private static void printUsage(PrintStream out) {
+ out.println("Usage: java ResourceManager [-format-state-store]");
+ out.println(" "
+ + "[-remove-application-from-state-store <appId>]" + "\n");
+ }
{code}
TO
{noformat}
Usage: yarn resourcemanager [-format-state-store]
[-remove..] <appId>
{noformat}
> 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,
> 0004-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)
