hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10092) Move up on to log4j2
Date Wed, 04 Jun 2014 16:47:01 GMT

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

stack commented on HBASE-10092:
-------------------------------

How to progress on this [~andrew.purtell@gmail.com]?

+ Need to make tgzs and see that stuff lands in right place.  Add some excludes for transitive
includes of old log4js.
+ Need to try in standalone, pseudo, and cluster and bring up shell to make sure logs are
ending up in right place?

I'd be tempted to just commit something that basically worked and then work out the rest in
subsequent issues.

> Move up on to log4j2
> --------------------
>
>                 Key: HBASE-10092
>                 URL: https://issues.apache.org/jira/browse/HBASE-10092
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: stack
>         Attachments: 10092.txt, 10092v2.txt, HBASE-10092.patch
>
>
> Allows logging with less friction.  See http://logging.apache.org/log4j/2.x/  This rather
radical transition can be done w/ minor change given they have an adapter for apache's logging,
the one we use.  They also have and adapter for slf4j so we likely can remove at least some
of the 4 versions of this module our dependencies make use of.
> I made a start in attached patch but am currently stuck in maven dependency resolve hell
courtesy of our slf4j.  Fixing will take some concentration and a good net connection, an
item I currently lack.  Other TODOs are that will need to fix our little log level setting
jsp page -- will likely have to undo our use of hadoop's tool here -- and the config system
changes a little.
> I will return to this project soon.  Will bring numbers.
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message