[jira] (AMBARI-19783) Any ambari configuration change leads to an entire druid cluster restart

[Nishant Bangarwa (JIRA)]

Title: Message Title

Nishant Bangarwa created an issue   Ambari / AMBARI-19783 Any ambari configuration change leads to an entire druid cluster restart Issue Type: Bug Assignee: Nishant Bangarwa Created: 30/Jan/17 16:26 Priority: Major Reporter: Nishant Bangarwa Currently making any config change to one of the druid nodes leads to cluster restart for entire druid cluster including All the node types even if there is no change in those node configs. In Druid configs following changes needs to be done - 1) Move node specific config dependencies to component level instead of defining them for each service. 2) Remove dependencies on hdfs and yarn configs, Since druid does not maintain its own copy of those configs, we should not need to restart druid nodes on any config changes in MR/Yarn configs. Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)