You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2024/10/16 18:35:00 UTC

[jira] [Created] (HBASE-28919) Soft drop for destructive table actions

Andrew Kyle Purtell created HBASE-28919:
-------------------------------------------

             Summary: Soft drop for destructive table actions
                 Key: HBASE-28919
                 URL: https://issues.apache.org/jira/browse/HBASE-28919
             Project: HBase
          Issue Type: New Feature
          Components: master, snapshots
            Reporter: Andrew Kyle Purtell
            Assignee: Andrew Kyle Purtell
         Attachments: Soft Drop for Destructive Table Actions.pdf

When we administratively drop a table column or entire table, or truncate a table, the process begins rapidly. Procedures are scheduled for immediate execution that then modify or remove descriptors and state in META and on disk, and take unrecoverable actions at the HDFS layer. Although HFiles are copied to the archive in a destructive action, recovery scenarios are not automatic and involve some operator labor to reconstruct the table and re-import the archived data. If the HFileCleaner is not properly configured to facilitate such recovery then some data is not recoverable soon after procedure execution commences and all affected data is not recoverable within minutes. A customer faced with such an accident will be unhappy because the recovery scenarios available to them from this will involve either a restore from backup or from an earlier snapshot, and any changes committed more recently than the time of the last backup or last snapshot will be lost. 

Design document is attached. 

I have a *working implementation* of this proposal based on a fork of branch-2.5. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)