[
https://issues.apache.org/jira/browse/HBASE-15584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323932#comment-15323932
]
Matteo Bertozzi commented on HBASE-15584:
-----------------------------------------
that shows that FullTableBackupProcedure does not provide enough information to
understand which backup is in progress.
If you look at CreateTableProcedure it tells you which table is working on. and
more information can be added.
([~syuanjiang] can provide you more info about how to show more info in the
list_procedures)
so, to me this is just a matter of having the FullTableBackupProcedure
providing more info for the list_procedure. there is no need for a backup id
and another abort operation.
> Revisit handling of BackupState#CANCELLED
> -----------------------------------------
>
> Key: HBASE-15584
> URL: https://issues.apache.org/jira/browse/HBASE-15584
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Priority: Minor
>
> During review of HBASE-15411, Enis made the following point:
> {code}
> nobody puts the backup in cancelled state. setCancelled() is not used. So if
> I abort a backup, who writes to the system table the new state?
> Not sure whether this is a phase 1 patch issue or due to this patch. We can
> open a new jira and address it there if you do not want to do it in this
> patch.
> Also maybe this should be named ABORTED rather than CANCELLED.
> {code}
> This issue is to decide whether this state should be kept (e.g. through
> notification from procedure V2 framework in response to abortion).
> If it is to be kept, the state should be renamed ABORTED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
