Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 22 Nov 2011 22:46:40 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <240931964.4295.1322002000208.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1431927413.33538.1321407411659.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3408) yarn-daemon.sh unconditionnaly
 sets yarn.root.logger
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MAPREDUCE-3408?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13155525#comment-13155525 ]=20

Hudson commented on MAPREDUCE-3408:
-----------------------------------

Integrated in Hadoop-Hdfs-0.23-Commit #203 (See [https://builds.apache.org/=
job/Hadoop-Hdfs-0.23-Commit/203/])
    MAPREDUCE-3408. yarn-daemon.sh unconditionnaly sets yarn.root.logger (B=
runo Mahe via mahadev) - Merging r1205200 from trunk

mahadev : http://svn.apache.org/viewcvs.cgi/?root=3DApache-SVN&view=3Drev&r=
ev=3D1205201
Files :=20
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/=
bin/yarn-daemon.sh

               =20
> yarn-daemon.sh unconditionnaly sets yarn.root.logger
> ----------------------------------------------------
>
>                 Key: MAPREDUCE-3408
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3408
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, nodemanager, resourcemanager
>    Affects Versions: 0.23.0, 0.23.1
>            Reporter: Bruno Mah=C3=A9
>            Assignee: Bruno Mah=C3=A9
>              Labels: bigtop
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3408.patch
>
>
> yarn-daemon.sh unconditionnaly sets yarn.root.logger which then prevent a=
ny override from happening.
> From ./hadoop-mapreduce-project/hadoop-yarn/bin/yarn-daemon.sh:
> > export YARN_ROOT_LOGGER=3D"INFO,DRFA"
> > export YARN_JHS_LOGGER=3D"INFO,JSA"
> and then yarn-daemon.sh will call "$YARN_HOME"/bin/yarn which does the fo=
llowing:
> > YARN_OPTS=3D"$YARN_OPTS -Dhadoop.root.logger=3D${YARN_ROOT_LOGGER:-INFO=
,console}"
> > YARN_OPTS=3D"$YARN_OPTS -Dyarn.root.logger=3D${YARN_ROOT_LOGGER:-INFO,c=
onsole}"
> This has at least 2 issues:
> * I cannot override hadoop.root.logger when using the yarn-daemon.sh scri=
pt
> * I cannot have different values for hadoop.root.logger and yarn.root.log=
ger
> I currently see two different ways to proceed forward:
> 1/ Make the script yarn-daemon.sh only sets a default value for YARN_ROOT=
_LOGGER if this variable is not defined
> 2/ Remove the quoted code from yarn-daemon.sh since yarn already does som=
ething similar
> 3/ Entirely remove that chunk and let people define their logging however=
 they want through some properties files (see log4j.properties in the conf =
directories for instance)
> I would also use the variable HADOOP_ROOT_LOGGER for hadoop.root.logger i=
f either option 1/ or 2/ would be taken.
> I don't really have any preference toward any of these solutions. What wo=
uld you recommend? What is the Apache Hadoop way for this matter?
> Note: This is probably happening as well for the other daemons, and I wil=
l take a look at it once this issue is resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira