[
https://issues.apache.org/jira/browse/AMBARI-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srimanth Gunturi updated AMBARI-3531:
-------------------------------------
Description:
Ambari currently provides cluster level service configurations.
This is a problem when the cluster has a mix of different hardwares requiring
different configurations for a group of hosts of a service. For example, some
DataNodes having bigger disks might need extra mount points in
{{dfs_datanode_data_dir}}.
Ambari needs to provide configuration override capability for a group of hosts
per service.
The primary use cases from UI perspective are:
* Override 3 properties for 500 hosts
* Go to host and see effective configurations
* Save configuration without restarting
* Indicate which services/components need restarting
was:
Ambari currently provides cluster level service configurations.
This is a problem when the cluster has a mix of different hardwares requiring
different configurations for a group of hosts of a service. For example, some
DataNodes having bigger disks might need extra mount points in
{{dfs_datanode_data_dir}}.
Ambari needs to provide configuration override capability for a group of hosts
per service.
> Provide configuration host overrides capability in Ambari
> ---------------------------------------------------------
>
> Key: AMBARI-3531
> URL: https://issues.apache.org/jira/browse/AMBARI-3531
> Project: Ambari
> Issue Type: New Feature
> Components: controller
> Affects Versions: 1.4.1
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 1.4.2
>
>
> Ambari currently provides cluster level service configurations.
> This is a problem when the cluster has a mix of different hardwares requiring
> different configurations for a group of hosts of a service. For example, some
> DataNodes having bigger disks might need extra mount points in
> {{dfs_datanode_data_dir}}.
> Ambari needs to provide configuration override capability for a group of
> hosts per service.
> The primary use cases from UI perspective are:
> * Override 3 properties for 500 hosts
> * Go to host and see effective configurations
> * Save configuration without restarting
> * Indicate which services/components need restarting
--
This message was sent by Atlassian JIRA
(v6.1#6144)
