[
https://issues.apache.org/jira/browse/HBASE-15292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304387#comment-15304387
]
Hudson commented on HBASE-15292:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1220 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1220/])
HBASE-15292 Refined ZooKeeperWatcher to prevent ZooKeeper's callback (apurtell:
rev c7445edd627bee2ad822691de9475b0ce0264a87)
*
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/PendingWatcher.java
*
hbase-client/src/test/java/org/apache/hadoop/hbase/zookeeper/TestInstancePending.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/InstancePending.java
> Refined ZooKeeperWatcher to prevent ZooKeeper's callback while construction
> ---------------------------------------------------------------------------
>
> Key: HBASE-15292
> URL: https://issues.apache.org/jira/browse/HBASE-15292
> Project: HBase
> Issue Type: Bug
> Components: Zookeeper
> Reporter: Hiroshi Ikeda
> Assignee: Hiroshi Ikeda
> Priority: Minor
> Fix For: 2.0.0, 1.3.0, 1.4.0, 0.98.20
>
> Attachments: HBASE-15292-V2.patch, HBASE-15292-V3.patch,
> HBASE-15292-V4.patch, HBASE-15292-V5.patch, HBASE-15292.patch
>
>
> The existing code is not just messy but also contains a subtle bug of
> visibility due to missing synchronization between threads.
> The root of the evil is that ZooKeeper uses a silly anti-pattern, starting a
> thread within its constructor, and in practice all the developers are not
> allowed to use ZooKeeper correctly without tedious code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
