[
https://issues.apache.org/jira/browse/HBASE-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410692#comment-13410692
]
Jesse Yates commented on HBASE-6205:
------------------------------------
bq. If not, if tester has access to both, IMO more safeguards will never fully
protect against this error happening.
True, but we can be really good about it.
By combining a timeout before actually deleting a table (so you can do a quick
restore) with a snapshot of the deleted table and a further timeout before the
snapshot is cleaned (similar to the log-cleaner stuff now) - giving you a
slower restore from saved state - you can minimize impact on the cluster and
still keep most of the data safe. Unless you accidentally delete a table and
then walk away for a week, you will probably be fine.
> Support an option to keep data of dropped table for some time
> -------------------------------------------------------------
>
> Key: HBASE-6205
> URL: https://issues.apache.org/jira/browse/HBASE-6205
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 0.94.0, 0.96.0
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.96.0
>
> Attachments: HBASE-6205.patch, HBASE-6205v2.patch,
> HBASE-6205v3.patch, HBASE-6205v4.patch, HBASE-6205v5.patch
>
>
> User may drop table accidentally because of error code or other uncertain
> reasons.
> Unfortunately, it happens in our environment because one user make a mistake
> between production cluster and testing cluster.
> So, I just give a suggestion, do we need to support an option to keep data of
> dropped table for some time, e.g. 1 day
> In the patch:
> We make a new dir named .trashtables in the rood dir.
> In the DeleteTableHandler, we move files in dropped table's dir to trash
> table dir instead of deleting them directly.
> And Create new class TrashCleaner which will clean dropped tables if it is
> time out with a period check.
> Default keep time for dropped tables is 1 day, and check period is 1 hour.
--
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
