hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.
Date Thu, 21 Nov 2013 04:15:53 GMT

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

Xuan Gong commented on YARN-1320:
---------------------------------

bq. Seems like we don't need to pass anything to the AM. AM can verify if a file by name log4j.properties
exists and use it.
So, the cmd line option log_properties to AM can be removed.

REMOVED

bq. In the client, you can use the "logj4Path" constant while setting up the localResource.

Changed

bq.Link this JIRA to YARN-1303 and reuse test-code?

We can re-use the code

> Custom log4j properties in Distributed shell does not work properly.
> --------------------------------------------------------------------
>
>                 Key: YARN-1320
>                 URL: https://issues.apache.org/jira/browse/YARN-1320
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: applications/distributed-shell
>            Reporter: Tassapol Athiapinya
>            Assignee: Xuan Gong
>         Attachments: YARN-1320.1.patch, YARN-1320.2.patch, YARN-1320.3.patch, YARN-1320.4.patch,
YARN-1320.4.patch, YARN-1320.4.patch, YARN-1320.4.patch, YARN-1320.4.patch, YARN-1320.5.patch,
YARN-1320.6.patch, YARN-1320.6.patch, YARN-1320.7.patch, YARN-1320.8.patch
>
>
> Distributed shell cannot pick up custom log4j properties (specified with -log_properties).
It always uses default log4j properties.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message