[
https://issues.apache.org/jira/browse/HBASE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159798#comment-13159798
]
Hudson commented on HBASE-4797:
-------------------------------
Integrated in HBase-0.92 #163 (See
[https://builds.apache.org/job/HBase-0.92/163/])
HBASE-4869 Backport to 0.92: HBASE-4797 [availability] Skip recovered.edits
files with edits older than what region currently has (Jimmy
Xiang)
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
> [availability] Skip recovered.edits files with edits we know older than what
> region currently has
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-4797
> URL: https://issues.apache.org/jira/browse/HBASE-4797
> Project: HBase
> Issue Type: Bug
> Components: performance
> Reporter: stack
> Assignee: Jimmy Xiang
> Priority: Critical
> Labels: noob
> Fix For: 0.94.0
>
> Attachments: 0001-HBASE-4797-[availability]-skip-older-edits.patch,
> 0001-HBASE-4797-[availability]-skip-older-edits.patch,
> 0001-HBASE-4797-availability-skip-files-with-edits-we-kno.patch,
> 0001-HBASE-4797-availability-skip-files-with-edits-we-kno.patch
>
>
> 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
