hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1185) dynamically change dfs log levels
Date Tue, 30 Oct 2007 22:15:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538933
] 

Hadoop QA commented on HADOOP-1185:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12368715/1185_20071030b.patch
against trunk revision r590273.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests -1.  The patch failed core unit tests.

    contrib tests -1.  The patch failed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1033/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1033/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1033/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1033/console

This message is automatically generated.

> dynamically change dfs log levels
> ---------------------------------
>
>                 Key: HADOOP-1185
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1185
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: 1185_20071030b.patch
>
>
> I would like to switch on the debug log level of the namenode without restarting it.
This is needed to analyze a production system.
> Can somebody please advice on how to set the loglevel dyncamically on a running namenode?
I was thinking of enhancing dfsadmin to make an RPC to the namenode to set a specified logging
level. But the apache common logging APi does not export an API to change logging levels.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message