At this point, I am +1 for a revert of the patch that introduced the problem (ZOOKEEPER-1371). We need more time to come up with a migration path to Log4J 2 that minimizes impact on operators. That will take time, and I'd prefer that we don't hold up 3.5.2-alpha for it.
--Chris Nauroth On 3/15/16, 11:08 AM, "Patrick Hunt" <[email protected]> wrote: >Hi folks, can we prioritize getting logging fixed? It's causing test >failures, e.g.: >https://builds.apache.org/job/ZooKeeper-trunk/2850/artifact/trunk/build/tm >p/zk.log > >This is the jira: >https://issues.apache.org/jira/browse/ZOOKEEPER-2342 > > >Perhaps we should revert the change that caused this in the first place. > >Patrick >
