[
https://issues.apache.org/jira/browse/YARN-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372472#comment-14372472
]
Hadoop QA commented on YARN-3241:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12706102/YARN-3241.002.patch
against trunk revision 7f1e2f9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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 following test timeouts occurred in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/7058//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7058//console
This message is automatically generated.
> Leading space, trailing space and empty sub queue name may cause
> MetricsException for fair scheduler
> ----------------------------------------------------------------------------------------------------
>
> Key: YARN-3241
> URL: https://issues.apache.org/jira/browse/YARN-3241
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Reporter: zhihai xu
> Assignee: zhihai xu
> Attachments: YARN-3241.000.patch, YARN-3241.001.patch,
> YARN-3241.002.patch
>
>
> Leading space, trailing space and empty sub queue name may cause
> MetricsException(Metrics source XXX already exists! ) when add application to
> FairScheduler.
> The reason is because QueueMetrics parse the queue name different from the
> QueueManager.
> QueueMetrics use Q_SPLITTER to parse queue name, it will remove Leading space
> and trailing space in the sub queue name, It will also remove empty sub queue
> name.
> {code}
> static final Splitter Q_SPLITTER =
> Splitter.on('.').omitEmptyStrings().trimResults();
> {code}
> But QueueManager won't remove Leading space, trailing space and empty sub
> queue name.
> This will cause out of sync between FSQueue and FSQueueMetrics.
> QueueManager will think two queue names are different so it will try to
> create a new queue.
> But FSQueueMetrics will treat these two queue names as same queue which will
> create "Metrics source XXX already exists!" MetricsException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
