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

Akhil S Naik updated AMBARI-23448:
----------------------------------
    Description: 
*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.







  was:
*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
 !Screen Shot 2018-04-04 at 5.01.42 PM.png! 





> 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-2.6.1.5
> HDP-2.6.4
>            Reporter: Akhil S Naik
>            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
(v7.6.3#76005)

Reply via email to