[
https://issues.apache.org/jira/browse/HBASE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974190#comment-16974190
]
Wellington Chevreuil edited comment on HBASE-23293 at 11/14/19 12:23 PM:
-------------------------------------------------------------------------
{quote}
Hi Wellington Chevreuil, you mean the original timeout is infinite ?
I have encounted timeout exceptions recently, thanks for your comments, will
dig it more.
{quote}
Ah, so without this change, it's using whatever is configured in the
*hbase.rpc.timeout* (60 seconds, by default), and that's timing out the
replication rpc in some bulkloads? Then main goal of this change is providing
an alternative valve for increasing the timeout?
was (Author: wchevreuil):
{quote}
Hi Wellington Chevreuil, you mean the original timeout is infinite ?
I have encounted timeout exceptions recently, thanks for your comments, will
dig it more.
{quote}
Ah, so without this change, it's using whatever is configured in the
*hbase.rpc.timeout* (60 seconds, by default), and that's timing out the
replication rpc in some bulkloads?
> [REPLICATION] make ship edits timeout configurable
> --------------------------------------------------
>
> Key: HBASE-23293
> URL: https://issues.apache.org/jira/browse/HBASE-23293
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: chenxu
> Assignee: chenxu
> Priority: Minor
>
> ReplicationSourceShipper#shipEdits may take a while if bulkload replication
> enabled, since we should copy HFile from the source cluster, so i think there
> is a need to make the timeout value configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
