[
https://issues.apache.org/jira/browse/HBASE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974317#comment-16974317
]
Pankaj Kumar commented on HBASE-23293:
--------------------------------------
{quote}What if the configured timeout is not sufficient?
{quote}
That is why we need to make it adpative, timeout should be adopted based on the
retry attempt.
For example, timeout should be increased by some multiplier (say 2) on each
retry. Like 60 sec (replication.source.shipedits.timeout) should be 120 second
on 2nd retry attempt and 240 sec on 3rd retry attempt. There should be some max
timedout value.
> [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)
