[
https://issues.apache.org/jira/browse/HBASE-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872013#comment-13872013
]
Hudson commented on HBASE-10335:
--------------------------------
FAILURE: Integrated in hbase-0.96-hadoop2 #176 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/176/])
HBASE-10335 AuthFailedException in zookeeper may block replication forever (Liu
Shaohui) (liangxie: rev 1558302)
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java
> AuthFailedException in zookeeper may block replication forever
> --------------------------------------------------------------
>
> Key: HBASE-10335
> URL: https://issues.apache.org/jira/browse/HBASE-10335
> Project: HBase
> Issue Type: Bug
> Components: Replication, security
> Affects Versions: 0.94.15, 0.99.0
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Blocker
> Fix For: 0.98.0, 0.96.2, 0.99.0, 0.94.17
>
> Attachments: HBASE-10335-v1.diff, HBASE-10335-v2.diff
>
>
> ReplicationSource will rechoose sinks when encounted exceptions during
> skipping edits to the current sink. But if the zookeeper client for peer
> cluster go to AUTH_FAILED state, the ReplicationSource will always get
> AuthFailedException. The ReplicationSource does not reconnect the peer,
> because reconnectPeer only handle ConnectionLossException and
> SessionExpiredException. As a result, the replication will print log:
> {quote}
> 2014-01-14,12:07:06,892 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Getting 0
> rs from peer cluster # 20
> 2014-01-14,12:07:06,892 INFO
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource: Slave
> cluster looks down: 20 has 0 region servers
> {quote}
> and be blocked forever.
> I think other places may have same problems for not handling
> AuthFailedException in zookeeper. eg: HBASE-8675.
> [~apurtell]
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
