hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17675) ReplicationEndpoint should choose new sinks if a SaslException occurs
Date Wed, 22 Feb 2017 06:10:44 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877545#comment-15877545
] 

Hudson commented on HBASE-17675:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #104 (See [https://builds.apache.org/job/HBase-1.2-JDK7/104/])
HBASE-17675 ReplicationEndpoint should choose new sinks if a (apurtell: rev 3c7e96a6fde2fad85483631032c7526a96e49f22)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java


> ReplicationEndpoint should choose new sinks if a SaslException occurs 
> ----------------------------------------------------------------------
>
>                 Key: HBASE-17675
>                 URL: https://issues.apache.org/jira/browse/HBASE-17675
>             Project: HBase
>          Issue Type: Bug
>            Reporter: churro morales
>            Assignee: churro morales
>             Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 1.1.9
>
>         Attachments: HBASE-17675.patch
>
>
> We had an issue where a regionserver on our destination side failed to refresh the keytabs.
 The source side's replication got stuck because the HBaseInterClusterReplicationEndpoint
only chooses new sinks if there happens to be a ConnectException but the SaslException is
an IOException, which does not choose new sinks.  
> I'll put up a patch to check this exception and choose new sinks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message