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 27B4118A09 for ; Mon, 7 Dec 2015 10:03:18 +0000 (UTC) Received: (qmail 29439 invoked by uid 500); 7 Dec 2015 10:03:11 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 29311 invoked by uid 500); 7 Dec 2015 10:03:11 -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 29291 invoked by uid 99); 7 Dec 2015 10:03:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Dec 2015 10:03:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 071C62C1F5A for ; Mon, 7 Dec 2015 10:03:11 +0000 (UTC) Date: Mon, 7 Dec 2015 10:03:11 +0000 (UTC) From: "Ashish Singhi (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (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 Ashish Singhi created HBASE-14937: ------------------------------------- Summary: 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 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)