Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 19 Feb 2016 10:41:18 +0000 (UTC)
From: "Hiroshi Ikeda (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12940463.1455878474000.92496.1455878478184@Atlassian.JIRA>
In-Reply-To: <JIRA.12940463.1455878474000@Atlassian.JIRA>
References: <JIRA.12940463.1455878474000@Atlassian.JIRA>
 <JIRA.12940463.1455878474040@arcas>
Subject: [jira] [Created] (HBASE-15292) Refined ZooKeeperWatcher to prevent
 ZooKeeper's callback while construction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hiroshi Ikeda created HBASE-15292:
-------------------------------------

             Summary: 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
            Priority: Minor


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)