Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 18 Jun 2016 13:35:05 +0000 (UTC)
From: "Wilfred Spiegelenburg (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12980530.1466256858000.33659.1466256905314@Atlassian.JIRA>
In-Reply-To: <JIRA.12980530.1466256858000@Atlassian.JIRA>
References: <JIRA.12980530.1466256858000@Atlassian.JIRA> <JIRA.12980530.1466256858315@arcas>
Subject: [jira] [Created] (YARN-5272) FairScheduler handles "invalid" queue
 names inconsistently even after YARN-3241
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 18 Jun 2016 13:35:07 -0000

Wilfred Spiegelenburg created YARN-5272:
-------------------------------------------

             Summary: FairScheduler handles "invalid" queue names inconsistently even after YARN-3241
                 Key: YARN-5272
                 URL: https://issues.apache.org/jira/browse/YARN-5272
             Project: Hadoop YARN
          Issue Type: Bug
          Components: fairscheduler
    Affects Versions: 2.8.0
            Reporter: Wilfred Spiegelenburg
            Assignee: Wilfred Spiegelenburg


The fix used in YARN-3214 uses a the JDK trim() method to remove leading and trailing spaces. The QueueMetrics uses a guava based trim when it splits the queues.

The guava based trim uses the unicode definition of a white space which is different than the java trim as can be seen [here|https://docs.google.com/a/cloudera.com/spreadsheets/d/1kq4ECwPjHX9B8QUCTPclgsDCXYaj7T-FlT4tB5q3ahk/pub]

A queue name with a non-breaking white space will thus still cause the same "Metrics source XXX already exists!" MetricsException.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org