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

Jesse Yates commented on HBASE-5547:
------------------------------------

bq. Maybe checking existence is cheaper than reading znode content though?

I don't think it would be appreciable. It still has to to go memory to check 
existence, so the only loss is the time to write the content over the wire 
(negligible in our case when we have around a 1KB of configuration info).

bq. If we had a Configuration or Table znode, it could read the content

Certainly. But then there is the work to finish that code (HBASE-3909 if I'm 
not mistaken), which still seems a long way off. 

This may all (except for the table config stuff, which would be an arguably 
'better' version) be moot as I do have a version working now that does 
synchronous checking to make sure that all necessary RS received the update 
have updated zk that they have received the notification. Avoids the problem of 
splits/merges per region as its all on the RS level. There is still a bit of 
cleanup I need to do on the patch before posting the another review, but the 
core of the functionality is there.

                
> Don't delete HFiles when in "backup mode"
> -----------------------------------------
>
>                 Key: HBASE-5547
>                 URL: https://issues.apache.org/jira/browse/HBASE-5547
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Lars Hofhansl
>            Assignee: Jesse Yates
>
> This came up in a discussion I had with Stack.
> It would be nice if HBase could be notified that a backup is in progress (via 
> a znode for example) and in that case either:
> 1. rename HFiles to be delete to <file>.bck
> 2. rename the HFiles into a special directory
> 3. rename them to a general trash directory (which would not need to be tied 
> to backup mode).
> That way it should be able to get a consistent backup based on HFiles (HDFS 
> snapshots or hard links would be better options here, but we do not have 
> those).
> #1 makes cleanup a bit harder.

--
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