You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (Updated) (JIRA)" <ji...@apache.org> on 2011/11/16 19:42:52 UTC
[jira] [Updated] (HBASE-4797) [availability] Give recovered.edits
files better names, ones that include first and last sequence id so we can
skip files with edits we know older than current region has
[ https://issues.apache.org/jira/browse/HBASE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-4797:
-------------------------
Priority: Critical (was: Major)
Tags: noob
Labels: noob (was: )
> [availability] Give recovered.edits files better names, ones that include first and last sequence id so we can skip files with edits we know older than current region has
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4797
> URL: https://issues.apache.org/jira/browse/HBASE-4797
> Project: HBase
> Issue Type: Bug
> Components: performance
> Reporter: stack
> Priority: Critical
> Labels: noob
>
> Testing 0.92, I crashed all servers out. Another bug makes it so WALs are not getting cleaned so I had 7000 regions to replay. The distributed split code did a nice job and cluster came back but interesting is that some hot regions ended up having loads of recovered.edits files -- tens if not hundreds -- to replay against the region (can we bulk load recovered.edits instead of replaying them?). Each recovered.edits file is taking about a second to process (though only about 30 odd edits per file it seems). The region is unavailable during this time.
--
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