[
https://issues.apache.org/jira/browse/HBASE-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571757#comment-13571757
]
Eugene Koontz commented on HBASE-7771:
--------------------------------------
Good to see the ZK client latch being removed since the problem is fixed within
the ZK client!
Francis is right: the bad case would be if someone was running a secure cluster
and their packaging erroneously caused them to use a newer (post-HBASE-7771)
HBase jar but an older (pre-ZOOKEEPER-1437) Zookeeper jar. This would cause
HBase daemons to likely fail on restart, though - they would try to access
their private znodes and get AuthFailed from the Quorum. So this mismatch would
be immediately noticeable by operators.
> Secure HBase Client in MR job causes tasks to wait forever
> ----------------------------------------------------------
>
> Key: HBASE-7771
> URL: https://issues.apache.org/jira/browse/HBASE-7771
> Project: HBase
> Issue Type: Bug
> Reporter: Francis Liu
> Assignee: Francis Liu
> Fix For: 0.96.0, 0.94.5
>
> Attachments: 7771-0.94-combined.txt, 7771-combined.txt,
> HBASE-7771_94.patch, HBASE-7771-addendum-v0.patch, HBASE-7771.patch
>
>
> This seems to be a regression caused by HBASE-4791 wherein we check if secure
> zookeeper is enabled and if so we make use of saslLatch to verify security
> handshake is completed. But in the case of MR, we won't be negotiating a
> secure connection thus we end up waiting forever for the saslLatch.
> Since the bug the saslLatch workaround is trying to fix (ZOOKEEPER-1437) is
> already fixed in zookeeper-3.4.5. Removal of the workaround fixes the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
