hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10535) Table trash to recover table deleted by mistake
Date Mon, 17 Feb 2014 01:54:19 GMT

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

Jean-Marc Spaggiari commented on HBASE-10535:
---------------------------------------------

I also prefers to not use the .archive directory for this. When the TTL will expire, files
are going to be moved into .archive like other deleted files, but before that, it's not the
same usecase so I think it's correct to keep them aside.

Also, if we use a specific namespace and store the previous namespace in the new table name,
then we don't need to store that anywhere else.

> Table trash to recover table deleted by mistake
> -----------------------------------------------
>
>                 Key: HBASE-10535
>                 URL: https://issues.apache.org/jira/browse/HBASE-10535
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liu Shaohui
>            Priority: Minor
>
> When table is deleted, only Hfiles are moved to archives dir, table and region infos
are deleted immediately. So it's very difficult to recover tables which are deleted by mistakes.
> I think if we can introduce an table trash dir in HDFS. When the table is deleted, the
entire table dir is moved to trash dir. And after an configurable ttl,  the dir is deleted
actually. This can be done by HMaster.
> If we want to recover the deleted table, we can use a tool which moves table dir out
of trash and recovery the meta data of the table. There are many problems the recover tool
will encountered eg, parent  and daughter regions are all in the table dir. But I think this
feature is useful to handle some special cases.
> Discussions are welcomed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message