hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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
Date Wed, 16 Nov 2011 18:42:51 GMT

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

stack commented on HBASE-4797:
------------------------------

Thinking some more on this, we don't need to rename recovered.edits files.  The files are
named for the first sequenceid in the file, so, we could just do file listing and sort the
return.  Then we'd have range of sequenceids per file.  We could then just pass on files with
edits that are smaller than regions current seqid.
                
> [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
>              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

        

Mime
View raw message