[
https://issues.apache.org/jira/browse/HBASE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102712#comment-14102712
]
Andrew Purtell commented on HBASE-10092:
----------------------------------------
bq. I don't think properties is a blocker one way or another.
See Stack's comment above. The change will not be palatable for current or
anticipated releases (0.98, 1.0) without properties file compatibility. A trunk
only change would still be a great contribution but with less impact. I would
really like to see async logging a possibility in 0.98 so will need to do this
work at least in that branch.
bq. Any reason why we should not consider logback? It looks like supporting
unit testing with the new version of surefire is going to be very hard with
log4j2
Hadoop is looking at moving up to log4j2 also. What kind of hell will we be in
if Hadoop is on log4j2 and we are on logback? Isn't log4j2 the continuation of
logback?
> 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: Alex Newman
> Fix For: 2.0.0
>
> 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)
