You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "churro morales (JIRA)" <ji...@apache.org> on 2017/02/28 22:09:45 UTC

[jira] [Assigned] (HBASE-17698) ReplicationEndpoint choosing sinks

     [ https://issues.apache.org/jira/browse/HBASE-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

churro morales reassigned HBASE-17698:
--------------------------------------

    Assignee: Karan Mehta

> 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
>
> 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)