[
https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248088#comment-13248088
]
Uma Maheswara Rao G commented on HBASE-3909:
--------------------------------------------
@Subbu,
{quote}
Also @Uma you raised lot of interesting questions which I had while working on
this and I will post my thoughts on the same some time tomorrow.
{quote}
That's great.
Thinking some more, one more point to check.
Presently looks this design will update same set of configurations in all nodes
(Hmasters/ RegionServers). But Hmaster may not require or interested on
HRegionServer specific configuration items. But when you update the
configurations related to HRegionServer, call back will come to Hmaster as well
and will process this event. This processing will be really unnecessary in
Hmaster. Because it will never use that RegionServers specific configuration
items.
@Stack, Ted, what is your opinion on this point.
is it ok to update in all nodes as same? or we can separate the Znodes clearly
for Hmaster and HregionServer, and then updations will takes place accordingly?
I mean anyway we have to maintain reconfigurable items in-memory.So, here
itself we can distinguish them. And the property updations from admin can pass
to the correspondiong Znode based on item.
> 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
