hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6165) Replication can overrun .META scans on cluster re-start
Date Thu, 09 Aug 2012 17:50:19 GMT

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

Elliott Clark commented on HBASE-6165:
--------------------------------------

@Lars
We had this happen when a large cluster is replication to a small cluster.
Source (Large Cluster)
Sink (Small cluster)

After the sink goes down or re-starts, the source waits for meta to come up.  After that lots
of replicate wal edits are shipped to all the server.  So many in fact that the server holding
meta does not have any left to answer meta scans or edits.
                
> 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
>         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

        

Mime
View raw message