zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2342) Migrate to Log4J 2.
Date Thu, 06 Jun 2019 23:33:00 GMT

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

Michael Han commented on ZOOKEEPER-2342:
----------------------------------------

{quote}does anyone see an alternative way forward?
{quote}
We (twitter) have been using log4j2 with ZK for 2+ years and it's straightforward if backward
compatibility is not a concern (which was blocking this Jira moving forward iiuc). I certainly
would like this Jira making progress, because to use log4j2 we have to maintain a set of changes
(still manageable, but..) not in upstream, and these changes are not in a position to be upstreamed
because they does not address this JIRA's concern.

> Migrate to Log4J 2.
> -------------------
>
>                 Key: ZOOKEEPER-2342
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Major
>             Fix For: 3.6.0
>
>         Attachments: ZOOKEEPER-2342.001.patch
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that this also
removed the Log4J SLF4J binding jar from the runtime classpath.  Without any SLF4J binding
jar available on the runtime classpath, it is impossible to write logs.
> This JIRA investigated migration to Log4J 2 as a possible path towards resolving the
bug introduced by ZOOKEEPER-1371.  At this point, we know this is not feasible short-term.
 This JIRA remains open to track long-term migration to Log4J 2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message