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

Jonathan Hsieh commented on HBASE-6055:
---------------------------------------

Thanks Jesse,

I haven't looked at code yet but I got a chance to read through the writeup in 
HBASE-50.  One thing I like about it is that it breaks out the operations, 
pretty clearly describes the zk and hdfs layouts so that an admin, a tool, or 
someone with info at this particular level could use the feature and inspect 
the exposed zk and hdfs state for debugging. 

>From the HBASE-50 doc (haven't looked at code yet), Li seems to have chosen or 
>more clearly stated these design decisions:
- hlog roll (which I believe does not trigger a flush) instead of special meta 
hlog marker (this might avoid write unavailability, seems simpler that the 
mechanism I suggested) 
- admin initiated snapshot and admin initiated restore operations as opposed to 
acting like a read only table.  (not sure what happens to "newer" data after a 
restore, need to reread to see if it is in there, not sure about the cost to 
restore a snapshot)
- I believe it also has an ability to read files directly from an MR job 
without having to go through HBase's get/put interface.   Is that in scope for 
HBASE-6055?

Jon.

                
> Snapshots in HBase 0.96
> -----------------------
>
>                 Key: HBASE-6055
>                 URL: https://issues.apache.org/jira/browse/HBASE-6055
>             Project: HBase
>          Issue Type: New Feature
>          Components: client, master, regionserver, zookeeper
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.96.0
>
>         Attachments: Snapshots in HBase.docx
>
>
> Continuation of HBASE-50 for the current trunk. Since the implementation has 
> drastically changed, opening as a new ticket.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to