hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1185) dynamically change log levels
Date Thu, 01 Nov 2007 20:19:51 GMT

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

Doug Cutting commented on HADOOP-1185:

Sorry, I spoke out of context.  A generic command line option makes sense for setting the
log level of client programs, not daemons.  So someone should be able to specify '-loglevel
DEBUG' for any Hadoop command and have it affect the logging done by that command.  But that's
a separate issue from what's discussed here, and perhaps there's an easy way to do this already.
 (Is there?)

For the issue here, changing the log level of daemon processes, i agree that a separate command
is needed.  My preference might be something like:

  bin/hadoop daemonlog -setlevel host:port NAME LEVEL

We use the term 'daemon' to generically refer to all our daemons.  Perhaps the command could
also read logs with something like, 'bin/hadoop daemonlog -tail NAME'?  So the command might
provide generic access to the logs of our daemons.  That might not be supported in the first
version, but would be the long-term plan for the command.

> dynamically change log levels
> -----------------------------
>                 Key: HADOOP-1185
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1185
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.16.0
>            Reporter: dhruba borthakur
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 0.16.0
>         Attachments: 1185_20071031.patch
> I would like to switch on the debug log level of the namenode (or other components) 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.

View raw message