ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masahiro Tanaka (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-17253) Ambari Alerts causes too many wanings in ZooKeeper logs.
Date Wed, 15 Jun 2016 12:13:09 GMT
Masahiro Tanaka created AMBARI-17253:
----------------------------------------

             Summary: Ambari Alerts causes too many wanings in ZooKeeper logs.
                 Key: AMBARI-17253
                 URL: https://issues.apache.org/jira/browse/AMBARI-17253
             Project: Ambari
          Issue Type: Bug
            Reporter: Masahiro Tanaka
            Assignee: Masahiro Tanaka


There are too many WARNING in ZooKeeper log.

{code}
2016-06-15 21:02:15,405 - WARN  [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn@357]
- caught end of stream exception
EndOfStreamException: Unable to read additional data from client sessionid 0x0, likely client
has closed socket
        at org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
        at org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
        at java.lang.Thread.run(Thread.java:745)
{code}

It may be because of Ambari Alert. Ambari Alert pings to the zookeeper port to do monitoring.
We should use 'ruok' to monitor zookeepers.



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

Mime
View raw message