hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-433) region server should deleted restore log after successfull restore
Date Tue, 11 Mar 2008 22:26:46 GMT

     [ https://issues.apache.org/jira/browse/HBASE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Kellerman updated HBASE-433:
--------------------------------

    Attachment: patch.txt

HLog
- don't overwrite oldlogfile in splitLog if it already exists. Rename it and copy it into
the new oldlogfile. Then delete it once it has been copied.
- use FileUtil.fullyDelete to delete region server log directory.

HRegion
- delete oldlogfile once it has been successfully processed


> region server should deleted restore log after successfull restore
> ------------------------------------------------------------------
>
>                 Key: HBASE-433
>                 URL: https://issues.apache.org/jira/browse/HBASE-433
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.1.0
>            Reporter: Billy Pearson
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.1.0
>
>         Attachments: patch.txt
>
>
> Currently we do not remove the restore log "oldlogfile.log" after we reopen a region
after a crashed region server.
> Suggestion would be to remove after we successfully flush of all the edits to a mapfile
> so something like:
> replay log 
> memcache flush
> deleted log

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message