Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 Dec 2015 08:03:46 +0000 (UTC)
From: "Ashish Singhi (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12919632.1449482544000.51460.1450339426763@Atlassian.JIRA>
In-Reply-To: <JIRA.12919632.1449482544000@Atlassian.JIRA>
References: <JIRA.12919632.1449482544000@Atlassian.JIRA>
 <JIRA.12919632.1449482544166@arcas>
Subject: [jira] [Commented] (HBASE-14937) Make rpc call timeout for
 replication adaptive
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ashish Singhi commented on HBASE-14937:
---------------------------------------

Attached patch as per above approach mentioned.
On every retry we increase the timeout by (retry time * 2) if its value is not 0 or it reached Integer.Max_Value.

Please review.

> 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
(v6.3.4#6332)