[
https://issues.apache.org/jira/browse/HBASE-18016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001723#comment-16001723
]
Umesh Agashe commented on HBASE-18016:
--------------------------------------
bq. Currently, it is tricky and difficult (if not impossible) to undo deletions.
[~syuanjiang], Thanks for your comments. I agree. Currently I am thinking that
abort() can just abort/ kill the procedure with or without implementing
rollback. We noticed that once in a while procedure gets stuck (in waiting
state for an event thats never going to occur) and user can not do anything
about it. Its stuck in the system forever. Implementing abort with or without
rollback will help user clean up the stuck procedures. If procedure supports
rollback, abort will trigger rollback or else user can manually cleanup after
abort.
Let me know your thoughts.
> Implement abort for TruncateTableProcedure
> ------------------------------------------
>
> Key: HBASE-18016
> URL: https://issues.apache.org/jira/browse/HBASE-18016
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Fix For: 2.0.0
>
>
> TruncateTableProcedure can not be aborted as abort is not implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
