[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248491#comment-13248491
]
Uma Maheswara Rao G commented on HBASE-3909:
--------------------------------------------
{quote}
5. getMaster().updateConfig is not deprecated. It is used by the Shell.
{quote}
{code}
@Deprecated
public HMasterInterface getMaster()
But, I am not sure for wnat reason, this API has been deprecated.
{code}
{quote}
7. If ZK is down or connectivity is lost we have much bigger problem then
loosing a config update
{quote}
for example, i am referring HBASE-5635 kind of issues.
I think your 11th point mostly answering my 13th question. My 11th point was
something defferent. Since you want to make the initial patch simple, let's
discuss that later or separate task.
{quote}
13. My thought is ideally we want Master to be the single point of source for
all cluster wide config management/updates. We definitely don't want to
directly manipulate a RS specific property. I mean we should not expose API's
in RS to enable config key manipulations. Master should be the single point of
source for all configuration entries irrespective of whether the config is
cluster wide, master specific or RS specific and ZK should be the medium of
communication across the cluster. So, master will be involved in all config
updates is my take.
{quote}
I am not talking about the configuration updation from defferent nodes. I am
talking about some config item updations which may not be really required for
all the nodes. ( like some configurations items will be used only by master and
some items will be used only by RS). Anyway as you said, we can take this point
as next task I feel.
> 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
>
>
> 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
