[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294740#comment-13294740
]
Subbu M Iyer commented on HBASE-3909:
-------------------------------------
I am seeing that this is a complicated feature with lots of open questions.
1. There are lot of properties/configuration that may have no effect (even with
dynamic config tool) once the server is up. How do we communicate such cases?
Do we maintain a smaller subset of configurations that can be changed
dynamically and only allow those subsets for dynamic changes?
2. There are lot of properties that might take effect during cases of server
fail over/back up server taking over etc. Basically every dynamic configuration
change that we apply to the cluster will take effect during server failover/ or
back server taking over. How do we communicate such cases? Do we even want this?
3. Do we really think that this feature will be a valuable addition?
> Add dynamic config
> ------------------
>
> Key: HBASE-3909
> URL: https://issues.apache.org/jira/browse/HBASE-3909
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.96.0
>
> Attachments: 3909-v1.patch, 3909.v1, HBase Cluster Config
> Details.xlsx, patch-v2.patch
>
>
> 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.
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
