[
https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500501#comment-14500501
]
Hadoop QA commented on YARN-3410:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12726211/0004-YARN-3410.patch
against trunk revision c6b5203.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1207 javac
compiler warnings (more than the trunk's current 1181 warnings).
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationACLs
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesFairScheduler
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesApps
org.apache.hadoop.yarn.server.resourcemanager.security.TestAMRMTokens
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerQueueACLs
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
org.apache.hadoop.yarn.server.resourcemanager.TestSubmitApplicationWithRMHA
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/7381//testReport/
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/7381//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7381//console
This message is automatically generated.
> 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)
