Mark Payne created NIFI-1780:
--------------------------------
Summary: Investigate how we can tone down the ZooKeeper logs
Key: NIFI-1780
URL: https://issues.apache.org/jira/browse/NIFI-1780
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Mark Payne
We've had a few people mention seeing logs like the following in the nifi app
log:
2016-04-14 19:45:29,310 INFO [Framework Task Thread
Thread-2-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn Opening
socket connection to server localhost/127.0.0.1:2181. Will not attempt to
authenticate using SASL (unknown error)
2016-04-14 19:45:29,313 WARN [Framework Task Thread
Thread-2-SendThread(localhost:2181)] org.apache.zookeeper.ClientCnxn Session
0x0 for server null, unexpected error, closing socket connection and attempting
reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:1.8.0_45]
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
~[na:1.8.0_45]
at
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
~[na:na]
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) ~[na:na]
The first indicates that kerberos is not being used, but it sounds much scarier
when it indicates "unknown error". The second is a legitimate concern that it
is unable to connect, but it can be pretty concerning when it is repeated over
and over in the logs. We should see if we can reduce the amount of logs
generated here.
There also some other places where Zookeeper logging is quite verbose, such as
when a node running an embedded ZK server is disconnected from the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
