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

Posted to issues@hbase.apache.org by "Pankaj Kumar (Jira)" <ji...@apache.org> on 2019/11/14 08:55:00 UTC

[jira] [Commented] (HBASE-23293) [REPLICATION] make ship edits timeout configurable

    [ https://issues.apache.org/jira/browse/HBASE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974048#comment-16974048 ] 

Pankaj Kumar commented on HBASE-23293:
--------------------------------------

Thanks [~javaman_chen] for bringing this JIRA, can we make it adaptive rather than making it fix timedout always.

Fix timeout may not help when there is slow N/w and some file copy fails always to copy within the configured time. For example, if some HFile is big enough which may take more than 60 sec to be copied then it will always timedout.

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