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

Hudson commented on HBASE-12739:
--------------------------------

SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #725 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/725/])
HBASE-12739 Avoid too large identifier of ZooKeeperWatcher (Liu Shaohui) 
(stack: rev fa7e0a64640d4b4f59449e3b14694caaeb8914df)
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java


> Avoid too large identifier of ZooKeeperWatcher
> ----------------------------------------------
>
>                 Key: HBASE-12739
>                 URL: https://issues.apache.org/jira/browse/HBASE-12739
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>    Affects Versions: 0.94.11
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Minor
>             Fix For: 1.0.0, 2.0.0, 0.94.26, 0.98.10, 1.1.0
>
>         Attachments: HBASE-12739-trunk-v1.diff
>
>
> For each SyncConnected event,  the ZooKeeperWatcher will append the session 
> id to its identity.
> During the failover of zk, the zookeeper client can connect to the zk server, 
> but the the zk server can not serve the request, so the client will try 
> continually, which will produce many SyncConnected events and a very large 
> identifier of ZooKeeperWatcher in hbase log.
> {code}
> 2014-12-22,12:38:56,296 WARN org.apache.hadoop.hbase.zookeeper.ZKUtil: 
> master:16500-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-0x349cbb4e4a7f0ba-...
> {code}
> A simple patch to fix this problem.



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

Reply via email to