[
https://issues.apache.org/jira/browse/HBASE-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026518#comment-16026518
]
Karan Mehta commented on HBASE-18117:
-------------------------------------
{{ConfigurationManager}} manages all the observers and is meant to be a
singleton class, which is initialized inside the {{RSRpcServices}}. However, it
is declared as a package protected and hence it is difficult to make it useful
for other parameters which are being used by classes from different packages. A
better approach is to move this framework from {{hbase-server}} to
{{hbase-common}}. How does this approach seem? This framework can follow
singleton design pattern as well if required.
> Increase resiliency by allowing more parameters for online config change
> ------------------------------------------------------------------------
>
> Key: HBASE-18117
> URL: https://issues.apache.org/jira/browse/HBASE-18117
> Project: HBase
> Issue Type: Improvement
> Reporter: Karan Mehta
> Assignee: Karan Mehta
>
> HBASE-8544 adds the feature to change config online without having a server
> restart. This JIRA is to work on new parameters for the utilizing that
> feature.
> As [~apurtell] suggested, following are the useful and frequently changing
> parameters in production.
> - RPC limits, timeouts, and other performance relevant settings
> - Replication limits and batch sizes
> - Region carrying limit
> - WAL retention and cleaning parameters
> I will try to make the RPC timeout parameter online as a part of this JIRA.
> If it seems suitable then we can extend it to other params.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
