You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jerry He (JIRA)" <ji...@apache.org> on 2016/10/13 03:21:20 UTC

[jira] [Created] (HBASE-16822) Enable restore-snapshot and clone-snapshot to use external specified snapshot locatioin

Jerry He created HBASE-16822:
--------------------------------

             Summary: Enable restore-snapshot and clone-snapshot to use external specified snapshot locatioin 
                 Key: HBASE-16822
                 URL: https://issues.apache.org/jira/browse/HBASE-16822
             Project: HBase
          Issue Type: Improvement
            Reporter: Jerry He


Currently restore-snapshot and clone-snapshot only work with the snapshots that are under hbase root.dir.

In combination with export-snapshot, this means the snapshot needs to be exported out to another hbase root.dir, or back and forth eventually to a hbase root.dir.

There are a few issues with the approach.

We've know that export-snapshot has a limitation dealing with secure cluster, where the external user needs to have read access to hbase root.dir data, by-passing table ACL check.

The second problem is when we try to use or bring back the exported snapshot for restore/clone.  They have to in the target hbase root.dir, and needs write permission to get it in there.

Again we will have permission problem.

This ticket tries to deal with the second problem, clone and restore from a exported snapshot.  The exported snapshots can be on the same cluster but the user may not have write permission to move it to hbase.root.dir.

We should have a solution that allow clone/restore snapshot from a external path that keeps snapshot backups. And also do it with security permission in mind.





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