Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8740518E12 for ; Fri, 18 Dec 2015 17:58:48 +0000 (UTC) Received: (qmail 52345 invoked by uid 500); 18 Dec 2015 17:58:47 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 52232 invoked by uid 500); 18 Dec 2015 17:58:47 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 52181 invoked by uid 99); 18 Dec 2015 17:58:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2015 17:58:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BE34B2C1F74 for ; Fri, 18 Dec 2015 17:58:46 +0000 (UTC) Date: Fri, 18 Dec 2015 17:58:46 +0000 (UTC) From: "Ashish Singhi (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064339#comment-15064339 ] Ashish Singhi commented on HBASE-14937: --------------------------------------- Andrew, thanks for the comment. bq. When replication is down, say because of a network partition or temporary issue on one cluster, RPC calls cannot succeed and will time out. In this case we will get ConnectException, right ? Please correct me If I am wrong. > 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)