[
https://issues.apache.org/jira/browse/HBASE-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883719#comment-15883719
]
Andrew Purtell commented on HBASE-17698:
----------------------------------------
bq. 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.
I would be curious as to an answer for this question as well. Why not make a
change in HBaseInterClusterReplicationEndpoint like:
{code}
- } else if (ioe instanceof SaslException) {
- LOG.warn("Peer encountered SaslException, rechecking all sinks: ",
ioe);
+ } else {
+ LOG.warn("Peer encountered exception, rechecking all sinks: ",
ioe);
replicationSinkMgr.chooseSinks();
{code}
?
> ReplicationEndpoint choosing sinks
> ----------------------------------
>
> Key: HBASE-17698
> URL: https://issues.apache.org/jira/browse/HBASE-17698
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.4.0
> Reporter: churro morales
>
> 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)
