Ambud Sharma commented on AMBARI-23448:

Rack is an attribute of HOST in Ambari and not just HDFS. This information is 
available to ALL stacks that want to leverage Rack information.

broker.rack is dynamically set due to this feature for Kafka based on rack 
information from Ambari, if rack information is changed Ambari asks all 
affected services to be restarted i.e. it's not scoping to only restart the 
nodes who's rack information was changed.


Unfortunately there's no way (as far as I know) to make the below XML 
configuration dynamic, and this config is what tells Ambari to prompt a a 
service restart.


So it's either going to prompt a change if the rack info is changed or not at 

If there is NO prompt when Kafka rack info is changed users will be at a 
disadvantage since they won't realize there is pending.

IMO, this should be feature request to scope restarts in Ambari to affected 
nodes only that have changed rack information.


> Ambari is asking for KAFKA service to restart when the rack information is 
> changed for HDFS
> -------------------------------------------------------------------------------------------
>                 Key: AMBARI-23448
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23448
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.1
>         Environment: Ambari-
> HDP-2.6.4
>            Reporter: Akhil S Naik
>            Assignee: JaySenSharma
>            Priority: Major
>         Attachments: Screen Shot 2018-04-04 at 5.01.42 PM.png
> *when trying to change the default rack of datanodes and trying to set custom 
> rack the ambari-server is asking kafka service to restart.*
> attached screenshot as attachment.
> root Cause :
> Ambari is reading the configs of KAFKA service from metainfo.xml 
> in which its given 
> *<restartRequiredAfterRackChange>true</restartRequiredAfterRackChange>*
>  rack awareness configurations of HDFS and Kafka are different , ambari 
> should ask for restart of KAFKA when hdfs configurations are refreshed.

This message was sent by Atlassian JIRA

Reply via email to