hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4980) Incorrect logging.properties file for hadoop-httpfs
Date Fri, 12 Jul 2013 14:09:51 GMT

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

Hudson commented on HDFS-4980:
------------------------------

SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1485 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1485/])
HDFS-4980. Incorrect logging.properties file for hadoop-httpfs. Contributed by Mark Grover.
(suresh: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1502302)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/pom.xml
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

                
> Incorrect logging.properties file for hadoop-httpfs
> ---------------------------------------------------
>
>                 Key: HDFS-4980
>                 URL: https://issues.apache.org/jira/browse/HDFS-4980
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.0.4-alpha
>         Environment: Maven 3.0.2 on CentOS6.2
>            Reporter: Mark Grover
>            Assignee: Mark Grover
>             Fix For: 2.1.0-beta
>
>         Attachments: HADOOP-9721.1.patch
>
>
> Tomcat ships with a default logging.properties file that's generic enough to be used
however we already override it with a custom log file as seen at https://github.com/apache/hadoop-common/blob/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/pom.xml#L557
> This is necessary because we can have the log locations controlled by httpfs.log.dir
env variable (instead of default catalina.base/logs), control the prefix of the log files
names, etc.
> In any case, this overriding doesn't always happen. In my environment, the custom logging.properties
file doesn't get overridden. The reason is the destination logging.properties file already
exists and the maven pom's copy command silently fails and doesn't override. If we explicitly
delete the destination logging.properties file, then the copy command successfully completes.
You may notice, we do the same thing with server.xml (which doesn't have this problem). We
explicitly delete the destination file first and then copy it over. We should do the same
with logging.properties as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message