[
https://issues.apache.org/jira/browse/HBASE-21744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768732#comment-16768732
]
Sergey Shelukhin commented on HBASE-21744:
------------------------------------------
Hm... still cannot repro any of these test failures and logs look bogus.
Some tests that fail appear to have no test history, so I wonder if they are
broken and run only for this patch. Some seem to have HDFS errors on the log,
or even setup issues connecting to stuff, and setup-time NPEs in test code.
Locally, they pass. Not sure if this patch causes something bad or is just
unlucky
> timeout for server list refresh calls
> --------------------------------------
>
> Key: HBASE-21744
> URL: https://issues.apache.org/jira/browse/HBASE-21744
> Project: HBase
> Issue Type: Improvement
> Components: Zookeeper
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Attachments: HBASE-21744.01.patch, HBASE-21744.02.patch,
> HBASE-21744.03.patch, HBASE-21744.patch
>
>
> Not sure why yet, but we are seeing the case when cluster is in overall a bad
> state, where after RS dies and deletes its znode, the notification looks like
> it's lost, so the master doesn't detect the failure. ZK itself appears to be
> healthy and doesn't report anything special.
> After some other change is made to the server list, master rescans the list
> and picks up the stale change. Might make sense to add a config that would
> trigger the refresh if it hasn't happened for a while (e.g. 1 minute).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
