Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 15 Aug 2012 06:00:39 +1100 (NCT)
From: "Himanshu Vashishtha (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1725741428.8993.1344970839901.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HBASE-6550) Refactoring ReplicationSink to make
 it more responsive of cluster health
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Himanshu Vashishtha updated HBASE-6550:
---------------------------------------

    Attachment: HBase-6550.patch

Ok, I removed the bailout behavior. Attached is a patch. Replication tests pass; also did a smoke testing on a real cluster.
                
> Refactoring ReplicationSink to make it more responsive of cluster health
> ------------------------------------------------------------------------
>
>                 Key: HBASE-6550
>                 URL: https://issues.apache.org/jira/browse/HBASE-6550
>             Project: HBase
>          Issue Type: New Feature
>          Components: replication
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>         Attachments: 6550-havealook.txt, HBase-6550.patch, HBase-6550-v1.patch
>
>
> ReplicationSink replicates the WALEdits in the local cluster. It uses native HBase client to insert the mutations. Sometime, it takes a while to process it (may be due to region splitting, gc pause, etc) and it undergoes the retrial phase. 
> It has two repercussions:
> a) The regionserver handler which is serving the request (till now, a priority handler) is blocked for this period.
> b) The caller may get timed out and it will retry it anyway, but the handler serving the ReplicationSink requests is still working.
> Refactoring ReplicationSink to have the following features:
> a) Making it more configurable (have its own number of retrial limit, connection timeout, etc)
> b) Add a fail fast behavior so that it bails out in case caller is timedout, or any exception in processing the mutation batch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira