You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2020/05/08 09:03:00 UTC

[jira] [Commented] (HBASE-19577) Use log4j2 instead of log4j for logging

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

Duo Zhang commented on HBASE-19577:
-----------------------------------

OK, hadoop still reference log4j when setting up MiniDFSCluster. The related code is in FSNamesytem.enableAsyncAuditLog. Even if we do not call this method, it will still lead to a ClassNotFoundException...

So this means we still need to introduce log4j dpendencies, at least when running tests, which is really sad.

> Use log4j2 instead of log4j for logging
> ---------------------------------------
>
>                 Key: HBASE-19577
>                 URL: https://issues.apache.org/jira/browse/HBASE-19577
>             Project: HBase
>          Issue Type: Sub-task
>          Components: logging
>            Reporter: Michael Stack
>            Assignee: Duo Zhang
>            Priority: Major
>
> See HBASE-10092 for discussion. We have inserted slf4j as our frontend. Need to swap out the 5-year-old log4j1.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)