hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17007) Move ZooKeeper logging to its own log file
Date Fri, 04 Nov 2016 22:33:58 GMT

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

stack commented on HBASE-17007:
-------------------------------

NP. Just thought occassional pain correlating between the two logs rather than one on the
rare case of a zk issue small price to pay for some general clean up. Lets see if any other
opinions.

On sessionids, they will still be in the logs reported by our RecoverableZooKeeper.

We can't remove the duplication. ZK spews at INFO level and logs properties and CLASSPATH
duplicating our doing emissions of the same. Can't turn it off. 

Then there are also the occasional complaints from client like below (here it is timing around
shutdown):

2016-11-03 12:39:49,832 INFO  [M:0;172.21.1.131:61739] zookeeper.MiniZooKeeperCluster: Shutdown
MiniZK cluster with all ZK servers
2016-11-03 12:39:49,982 INFO  [172.21.1.131:61739.activeMasterManager-SendThread(localhost:2181)]
zookeeper.ClientCnxn: Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181.
Will not attempt to authenticate using SASL (unknown error)
2016-11-03 12:39:49,983 WARN  [172.21.1.131:61739.activeMasterManager-SendThread(localhost:2181)]
zookeeper.ClientCnxn: Session 0x1582ba35a740006 for server null, unexpected error, closing
socket connection and attempting reconnect
java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)

They are harmless but to a noobie operator, they probably look worrisome.

Thanks.

> Move ZooKeeper logging to its own log file
> ------------------------------------------
>
>                 Key: HBASE-17007
>                 URL: https://issues.apache.org/jira/browse/HBASE-17007
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Trivial
>         Attachments: 0001-HBASE-17007-Move-ZooKeeper-logging-to-its-own-log-fi.patch
>
>
> ZooKeeper logging can be too verbose. Lets move ZooKeeper logging to a different log
file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message