[
https://issues.apache.org/jira/browse/HBASE-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154773#comment-13154773
]
jirapos...@reviews.apache.org commented on HBASE-4797:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2906/
-----------------------------------------------------------
(Updated 2011-11-22 00:32:48.813017)
Review request for hbase, Todd Lipcon and Michael Stack.
Changes
-------
Revised patch with changes per review.
Summary
-------
If there are multiple recovered edits files, I used the file name to find the
initial sequence id. After these files are sorted, we can find a file's
possible maximum sequence id based on the next file's initial sequence id. If
the maximum sequence id is smaller than the current sequence id, the whole
recovered edits file is old and ignored.
This addresses bug HBASE-4797.
https://issues.apache.org/jira/browse/HBASE-4797
Diffs (updated)
-----
src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java 8b89661
src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java 5daa02b
Diff: https://reviews.apache.org/r/2906/diff
Testing
-------
Added test case to TestHRegion, and all the tests in this test are passed.
Thanks,
Jimmy
> [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
>
> 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
