You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/09/04 23:04:07 UTC
[jira] [Created] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Brandon Williams created CASSANDRA-4615:
-------------------------------------------
Summary: cannot set log4j level on modules/classes
Key: CASSANDRA-4615
URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.2.0 beta 1
Reporter: Brandon Williams
Priority: Minor
For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Comment Edited] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "David Alves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448107#comment-13448107 ]
David Alves edited comment on CASSANDRA-4615 at 9/5/12 9:15 AM:
----------------------------------------------------------------
right, you need to also down the threshold for the appender you want (probably the R one in this case).
I'll try and find find a better way to do that, but without actually using a different logger for tracing (and therefore changing quite a lot of code) it will probably depend on some weird hack to the logging system.
was (Author: dr-alves):
right, you need to also up the threshold for the appender you want (probably the R one in this case).
I'll try and find find a better way to do that, but without actually using a different logger for tracing (and therefore changing quite a lot of code) it will probably depend on some weird hack to the logging system.
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Commented] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448100#comment-13448100 ]
Jonathan Ellis commented on CASSANDRA-4615:
-------------------------------------------
I'm also not getting trace messages (e.g. from MessagingService) even when I set the root logger to TRACE in test/conf, btw.
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Commented] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448118#comment-13448118 ]
Jonathan Ellis commented on CASSANDRA-4615:
-------------------------------------------
so... upgrading the trace messages to debug wouldn't help us get debug from (just) gossip in the fileappender either, i take it?
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Commented] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "David Alves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448208#comment-13448208 ]
David Alves commented on CASSANDRA-4615:
----------------------------------------
not as long as the file appender has an INFO threshold, no.
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Commented] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "David Alves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448098#comment-13448098 ]
David Alves commented on CASSANDRA-4615:
----------------------------------------
The way it is setup right now, in order for tracing appender to be used in debug level, the root logger was set to DEBUG and the other appenders were set to INFO. This unfortunately has the side effect of not being able to lower only a particular logger to debug (because the root is already at debug).
The other strategy would be to have an alternative logger for tracing, but this cannot be done at the conf file level only, the actual instance of Logger would have to be a different one. I mean instead of Logger logger = LoggerFactory.getLogger(CassandraServer.class); we would have to use a particular one, like Logger logger = LoggerFactory.getLogger("tracing-logger");.
I chose the first one because it didn't mean changing code (just the conf file).
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Commented] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "David Alves (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448107#comment-13448107 ]
David Alves commented on CASSANDRA-4615:
----------------------------------------
right, you need to also up the threshold for the appender you want (probably the R one in this case).
I'll try and find find a better way to do that, but without actually using a different logger for tracing (and therefore changing quite a lot of code) it will probably depend on some weird hack to the logging system.
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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
[jira] [Assigned] (CASSANDRA-4615) cannot set log4j level on
modules/classes
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reassigned CASSANDRA-4615:
-----------------------------------------
Assignee: David Alves
Any ideas, David?
> cannot set log4j level on modules/classes
> -----------------------------------------
>
> Key: CASSANDRA-4615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4615
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Brandon Williams
> Assignee: David Alves
> Priority: Minor
>
> For example, setting log4j.logger.org.apache.cassandra.db=DEBUG in the config has no effect. Perhaps there is something else that needs to be set as well, but we should at least document that there.
--
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