Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 30 Aug 2016 22:12:20 +0000 (UTC)
From: "Daniel Templeton (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12999019.1471899624000.451567.1472595140614@Atlassian.JIRA>
In-Reply-To: <JIRA.12999019.1471899624000@Atlassian.JIRA>
References: <JIRA.12999019.1471899624000@Atlassian.JIRA> <JIRA.12999019.1471899624526@arcas>
Subject: [jira] [Commented] (YARN-5549)
 AMLauncher.createAMContainerLaunchContext() should not log the command to
 be launched indiscriminately
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 30 Aug 2016 22:12:22 -0000


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

Daniel Templeton commented on YARN-5549:
----------------------------------------

I just created YARN-5599 and YARN-5600 to help with debugging launch failures in a post-YARN-5549 world.  [~vinodkv], please correct the description of YARN-5599 to better reflect the reality of ATS if I'm off a bit.

> AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately
> ------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-5549
>                 URL: https://issues.apache.org/jira/browse/YARN-5549
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.2
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>            Priority: Critical
>         Attachments: YARN-5549.001.patch, YARN-5549.002.patch, YARN-5549.003.patch, YARN-5549.004.patch
>
>
> The command could contain sensitive information, such as keystore passwords or AWS credentials or other.  Instead of logging it as INFO, we should log it as DEBUG and include a property to disable logging it at all.  Logging it to a different logger would also be viable and may create a smaller administrative footprint.


--
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