hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Singhi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14937) Make rpc call timeout for replication adaptive
Date Fri, 18 Dec 2015 06:23:46 GMT

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

Ashish Singhi commented on HBASE-14937:

Thanks Ted for the review.

bq. Would the timeout increase too fast after several retries ?
Yes it might, if the network between two DC is very slow then it may take more time to finish
the replication request when it contains a mix of mutations and bulk loaded data and we have
not provided sufficient timeout value.

bq. Please include retry count in above message.
Already included in the next log message at info level below it.

bq. Should an upperbound be set for the total duration of retries ?
I purposefully did not set any upper bound to it reason being as stated in my first response.
If you would like to have a upper bound, what you suggest to be the maximum number of retries
before we give up increasing the timeout value ?

> Make rpc call timeout for replication adaptive
> ----------------------------------------------
>                 Key: HBASE-14937
>                 URL: https://issues.apache.org/jira/browse/HBASE-14937
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ashish Singhi
>            Assignee: Ashish Singhi
>              Labels: replication
>             Fix For: 2.0.0, 1.3.0
>         Attachments: HBASE-14937.patch
> When peer cluster replication is disabled and lot of writes are happening in active cluster
and later on peer cluster replication is enabled then there are chances that replication requests
to peer cluster may time out.
> This is possible after HBASE-13153 and it can also happen with many and many WAL data
replication still pending to replicate.
> Approach to this problem will be discussed in the comments.

This message was sent by Atlassian JIRA

View raw message