[
https://issues.apache.org/jira/browse/HBASE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256956#comment-13256956
]
stack commented on HBASE-5547:
------------------------------
bq. ...but is definitely a concern and something that I've seen take up to a
few seconds to propagate.
Yeah. If you don't want a window, query the regionservers (you'll need to add
something to query but...)
bq. ... Are you basically talking about doing per-table configuration storage
in the table znode?
I was stating then that we already are doing a per table attribute up in zk --
whether enabled or disabled -- and that rather than do up new nodes for a new
attribute that instead we should add to the table znode the new attribute.
That was then. Now I'm suggesting we put all config up there. We could start
w/ HTD if we want to keep it table scoped (we'd have another tier in front of
the one Nicolas added, a dynamic one).
If the above too ambitious, we should at least generalize the table znode so
can add attributes and we might as well pb serialize the HTD as anything else?
bq. ...If they are disabled, they need to check everytime to see if it has been
enabled
Or just watch the table znode and if it changes, check if backup has been
flipped on.
> 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
