[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037265#comment-13037265
]
Todd Lipcon commented on HBASE-3909:
------------------------------------
I'm always skeptical of the suggestion to store configuration in ZooKeeper.
Here's my reasoning:
- we already require at least one piece of configuration in the client itself
in order to connect to ZooKeeper (ie the ZK quorum info and session timeouts,
etc)
- operations teams are very good at managing text-based configuration files
with tools like puppet, cfengine, etc. It's also easy to version-control these
kinds of configs, add <!-- comments -->, etc. Moving to ZK makes these tasks
more difficult -- we'd need lots of tooling, etc.
- If we keep both the text-based and ZK-based, it's easy to accidentally change
something in ZK but forget to update in text, so it would revert on next
restart.
- we currently have the somewhat nice property that nothing in ZK is "critical"
- even if the ZK cluster is completely wiped out, we dont lose any info. This
would be a change.
> Add dynamic config
> ------------------
>
> Key: HBASE-3909
> URL: https://issues.apache.org/jira/browse/HBASE-3909
> Project: HBase
> Issue Type: Bug
> Reporter: stack
>
> I'm sure this issue exists already, at least as part of the discussion around
> making online schema edits possible, but no hard this having its own issue.
> Ted started a conversation on this topic up on dev and Todd suggested we
> lookd at how Hadoop did it over in HADOOP-7001
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
