You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/06/20 03:27:00 UTC

[jira] [Updated] (AMBARI-24032) Ambari should be selective about which HBase components that need to be restarted

     [ https://issues.apache.org/jira/browse/AMBARI-24032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated AMBARI-24032:
----------------------------
    Description: 
For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change.


One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes

  was:
For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change.

One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes


> Ambari should be selective about which HBase components that need to be restarted
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-24032
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24032
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Priority: Major
>
> For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change.
> One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)