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

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

bq. Yeah. If you don't want a window, query the regionservers (you'll need to 
add something to query but...)

I was trying to avoid making a change to the RS interface just for the check to 
see if it has propagated. However, this is a valid case, but requires a scan of 
META to see the regions and associated RS that need to be pinged. A little 
rough on IO, but certainly doable.

bq. ...If they are disabled, they need to check everytime to see if it has been 
enabled

Did this to minimize the latency for changes to propagate and minimize the zk 
logic for tracking nodes. If we tied the watching of the table znode 
state/config with updating the status, then yeah, this would be doable. I can 
see doing another set of property listeners for table properties - could 
actually be really nice. Wanna file a ticket?
                
> 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