hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6860) [replication] HBASE-6550 is too aggressive, DDOSes .META.
Date Fri, 21 Sep 2012 22:14:08 GMT

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

Hudson commented on HBASE-6860:

Integrated in HBase-TRUNK #3368 (See [https://builds.apache.org/job/HBase-TRUNK/3368/])
    HBASE-6860  [replication] HBASE-6550 is too aggressive, DDOSes .META. (Revision 1388694)

     Result = FAILURE
jdcryans : 
Files : 
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSink.java

> [replication] HBASE-6550 is too aggressive, DDOSes .META.
> ---------------------------------------------------------
>                 Key: HBASE-6860
>                 URL: https://issues.apache.org/jira/browse/HBASE-6860
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.94.2, 0.96.0
>         Attachments: HBASE-6860.patch
> I was doing maintenance on clusters and rebooting a replication slave was giving me a
lot of issues because the master wasn't able to read .META. while it was bombarded with getClosestRowBefore()
coming from all the ReplicationSinks. Since no regions are assigned, and it doesn't retry,
it goes straight back to the source which retries again.
> Also it seems that in some cases with retries=1 we don't even recover from a stale .META.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message