hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3909) Add dynamic config
Date Fri, 24 Feb 2012 00:45:50 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215277#comment-13215277
] 

stack commented on HBASE-3909:
------------------------------

I'm now suggesting we hoist the differences only up into zk.  We'd have a configuration directory
under /hbase in zk.  It would have znodes whose names are the config to change.  The content
of the znode is the new value (and type I suppose).

Once a znode is added under configuration dir, watchers are triggered and they update their
running Configuration instance.

We do some refactoring in HRegionServers and HMaster so important configs go back to their
Configuration instance at critical junctures such as at split or checking if should do a compaction
or if should flush, rather than read a data member that was set on Construction (We'd be careful
to not do lookup on Configuration always).

We'd add a configure to the shell that allowed you hoist configs up into zk.

We'd punt on there being a connection between this mechanism and whats in hbase-*xml.  This
facility is for 'ephemeral' configuration, for getting you over a temporary hump, for trying
out a setting to see its effect, or to get you out of a fix; e.g. cluster is up and running
but you forgot to set a critical config. all w/o need of a rolling restart/restart.
                
> 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.94.0
>
>
> 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

        

Mime
View raw message