You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Karan Mehta (JIRA)" <ji...@apache.org> on 2017/05/26 01:25:04 UTC

[jira] [Commented] (HBASE-18117) Increase resiliency by allowing more parameters for online config change

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

Karan Mehta commented on HBASE-18117:
-------------------------------------

The current framework only allows changes on the config parameters that are accessed only on the server side. If {{ConfigurationObserver}} is implemented by any of the classes from {{hbase-client}}, this will introduce a cyclic dependency between hbase-client and hbase-server projects and thus the build would fail. 

> 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)