hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-16571) Consider locking target table(s) during restore operation
Date Mon, 31 Oct 2016 19:49:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583546#comment-15583546
] 

Ted Yu edited comment on HBASE-16571 at 10/31/16 7:49 PM:
----------------------------------------------------------

With implementation moved to client side, implementing this would be trickier:
if table is locked but client dies prematurely, there is clean up work to be done.


was (Author: yuzhihong@gmail.com):
With implementation moved to client side, this doesn't seem to apply.

> Consider locking target table(s) during restore operation
> ---------------------------------------------------------
>
>                 Key: HBASE-16571
>                 URL: https://issues.apache.org/jira/browse/HBASE-16571
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>              Labels: backup
>
> During review of HBASE-15565, Stephen suggested taking table lock(s) on target table(s)
during restore operation.
> This would prevent admin from making accidental schema changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message