[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195864#comment-15195864
]
Patrick Hunt commented on ZOOKEEPER-2342:
-----------------------------------------
Should we backout ZOOKEEPER-1371 instead?
I don't see where we've done much thought on b/w compatibility. It's barely
mentioned on these two jiras. We need to consider both developers as well as
administrators. Perhaps this is just because I'm not familiar myself with
log4j2. (if so please tell me) I realize I need to go look into this more...
but that's part of my point. Is this something we really want to be changing
now?
Have we considered what other Hadoop ecosystem components are doing? e.g. is
this going to cause a problem for other components of hadoop and elsewhere that
rely on ZK and, for e.g., not yet moved to log4j2.
What's the impact on systems that need to manage ZK? e.g. do they need to
change the way they generate/edit/manage the log4j.conf file?
> ZooKeeper cannot write logs, because there is no SLF4J binding available on
> the runtime classpath.
> --------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Blocker
> Fix For: 3.5.2, 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, the it is
> impossible to write logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
