Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 8 Dec 2015 22:56:11 +0000 (UTC)
From: "Ashu Pachauri (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12920223.1449615359000.306752.1449615371202@Atlassian.JIRA>
In-Reply-To: <JIRA.12920223.1449615359000@Atlassian.JIRA>
References: <JIRA.12920223.1449615359000@Atlassian.JIRA>
 <JIRA.12920223.1449615359195@arcas>
Subject: [jira] [Created] (HBASE-14953)
 HBaseInterClusterReplicationEndpoint: Do not retry the whole batch of edits
 in case of RejectedExecutionException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ashu Pachauri created HBASE-14953:
-------------------------------------

             Summary: HBaseInterClusterReplicationEndpoint: Do not retry the whole batch of edits in case of RejectedExecutionException
                 Key: HBASE-14953
                 URL: https://issues.apache.org/jira/browse/HBASE-14953
             Project: HBase
          Issue Type: Bug
          Components: Replication
    Affects Versions: 2.0.0, 1.2.0, 1.3.0
            Reporter: Ashu Pachauri
            Assignee: Ashu Pachauri


When we have wal provider set to multiwal, the ReplicationSource has multiple worker threads submitting batches to HBaseInterClusterReplicationEndpoint. In such a scenario, it is quite common to encounter RejectedExecutionException because it takes quite long for shipping edits to peer cluster compared to reading edits from source and submitting more batches to the endpoint. 
The logs are just filled with warnings due to this very exception.

Since we subdivide batches before actually shipping them, we don't need to fail and resend the whole batch if one of the sub-batches fails with RejectedExecutionException. Rather, we should just retry the failed sub-batches. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)