[
https://issues.apache.org/jira/browse/HBASE-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710727#comment-16710727
]
Xu Cang commented on HBASE-21530:
---------------------------------
[~allan163]
bq. Aborting is not very useful to get out of stuck, *since some procedure is
not abortable.*
But can we make them abortable, at least for some procedures?
For example, *createNamespaceProcedure*. It's not abortable now, but I checked
the code, there are 5 states from it and I think it's fairly safe to abort from
any state. It might leave some data in namespace table or namespace ZK
directories. But these 2 ops are idempotent. (they can be re-ran multiple times
without causing any issue.) So there is no real issue aborting it.
Does this make sense to you? If so, I can start looking into adding some logic
here to make abort createNamespaceProcedure possible for branch-1.
(Branch-1 is still crucial to us and having AMv2 only on branch-2 doesn't help
resolving our issues.)
Thanks you
> Abort_Procedure should be able to take a list of proc IDs
> ---------------------------------------------------------
>
> Key: HBASE-21530
> URL: https://issues.apache.org/jira/browse/HBASE-21530
> Project: HBase
> Issue Type: Improvement
> Reporter: Geoffrey Jacoby
> Priority: Minor
>
> As a convenience, it would be helpful if the HBase shell's abort_procedure
> call had the option of taking in multiple procedure ids at the same time,
> rather than relying on operators to use a loop in an external script.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
