[
https://issues.apache.org/jira/browse/HBASE-19744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319559#comment-16319559
]
stack commented on HBASE-19744:
-------------------------------
bq. We still use it in AuthenticationTokenSecretManager. Do not know why it is
marked as deprecated since there is no alternate.
Yeah. I see that now. Looks like I marked it as deprecated years ago in
HBASE-5944. I need to dig. Perhaps it came alive again?
I need to figure why zk runs slow on my cluster. It is causing all kinds of zk
failures that no one else seems to see but are probably worth fixing so our zk
communication is more robust.
> Fix flakey TestZKLeaderManager
> ------------------------------
>
> Key: HBASE-19744
> URL: https://issues.apache.org/jira/browse/HBASE-19744
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments: 0001-HBASE-19744-Fix-flakey-TestZKLeaderManager.patch
>
>
> On my little cluster, zk runs slow for whatever reason (TBD). This test
> always fails on me. Looking at it, there is at least a race given we stop
> mock masters and then put them on line again immediately... Testing if a
> thread Master is not going to give right answer always. Also, given zk runs
> slow on this host, just up the timeouts and number of Masters available.
> Sloppy but more likely to succeed (This test is for a deprecated class...)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
