[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-07-13 Thread Siddharth Wagle (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siddharth Wagle updated AMBARI-17253:
-
Fix Version/s: 2.4.0

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.5.patch, 
> AMBARI-17253.6.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-07-13 Thread Siddharth Wagle (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siddharth Wagle updated AMBARI-17253:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to 2.4 and trunk, please close review.

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.5.patch, 
> AMBARI-17253.6.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-07-13 Thread Yusaku Sako (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yusaku Sako updated AMBARI-17253:
-
Priority: Critical  (was: Major)

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Critical
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.5.patch, 
> AMBARI-17253.6.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-07-11 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.6.patch

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.5.patch, 
> AMBARI-17253.6.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-07-08 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.5.patch

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.5.patch, 
> AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-07-04 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.4.patch

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.4.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-06-25 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.3.patch

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.2.patch, 
> AMBARI-17253.3.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-06-18 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.1.patch

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.1.patch, AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-06-18 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Affects Version/s: trunk
  Component/s: ambari-agent

> Ambari Alert causes too many wanings in ZooKeeper logs.
> ---
>
> Key: AMBARI-17253
> URL: https://issues.apache.org/jira/browse/AMBARI-17253
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-06-17 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Status: Patch Available  (was: Open)

> Ambari Alert 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
> Attachments: AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-06-17 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Attachment: AMBARI-17253.patch

> Ambari Alert 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
> Attachments: AMBARI-17253.patch
>
>
> 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)

[jira] [Updated] (AMBARI-17253) Ambari Alert causes too many wanings in ZooKeeper logs.

2016-06-15 Thread Masahiro Tanaka (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AMBARI-17253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Masahiro Tanaka updated AMBARI-17253:
-
Summary: Ambari Alert causes too many wanings in ZooKeeper logs.  (was: 
Ambari Alerts causes too many wanings in ZooKeeper logs.)

> Ambari Alert 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)