Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 9 Aug 2012 18:43:19 +0000 (UTC)
From: "Himanshu Vashishtha (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1202592420.2999.1344537799589.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <607303186.41423.1338930923040.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6165) Replication can overrun .META scans
 on cluster re-start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Himanshu Vashishtha commented on HBASE-6165:
--------------------------------------------

Lars, Ted and Elliot: Thanks for the feedback.


@Lars: Changing the name is beyond the scope of this jira, no? Another jira for that?
re: failfast: Yeah, the patch still uses HTablePool, but submits the batch in a threadpool (of ReplicationSink). Meanwhile, the handler keeps checking whether the client is still alive or not, while waiting for the task to finish. If the client is out, it cancels the task.
Also, ReplicationSink now has its own conf object where it can decorate it with its own timeout, number of retrials etc. Is there an open jira for ReplicationSink (can't create a jira yet)?
                
> Replication can overrun .META scans on cluster re-start
> -------------------------------------------------------
>
>                 Key: HBASE-6165
>                 URL: https://issues.apache.org/jira/browse/HBASE-6165
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Elliott Clark
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: HBase-6165-v1.patch
>
>
> When restarting a large set of regions on a reasonably small cluster the replication from another cluster tied up every xceiver meaning nothing could be onlined.

--
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