[
https://issues.apache.org/jira/browse/HBASE-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951999#comment-15951999
]
Hudson commented on HBASE-17698:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #136 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/136/])
HBASE-17698 ReplicationEndpoint choosing sinks (apurtell: rev
ea3907da7ba2fd8e9b86e0aee4c2198c8611faf2)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/HBaseInterClusterReplicationEndpoint.java
> ReplicationEndpoint choosing sinks
> ----------------------------------
>
> Key: HBASE-17698
> URL: https://issues.apache.org/jira/browse/HBASE-17698
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 2.0.0, 1.4.0
> Reporter: churro morales
> Assignee: Karan Mehta
> Fix For: 2.0.0, 1.4.0, 1.3.1, 1.1.9, 1.2.6
>
> Attachments: HBASE-17698.patch
>
>
> The only time we choose new sinks is when we have a ConnectException, but we
> have encountered other exceptions where there is a problem contacting a
> particular sink and replication gets backed up for any sources that try that
> sink
> HBASE-17675 occurred when there was a bad keytab refresh and the source was
> stuck.
> Another issue we recently had was a bad drive controller on the sink side and
> replication was stuck again.
> Is there any reason not to choose new sinks anytime we have a
> RemoteException? I can understand TableNotFound we don't have to choose new
> sinks, but for all other cases this seems like the safest approach.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
