@Kuldeep Kulkarni each service configuration can be updated by using API. Take a look here. You can also make changes in the blueprint. Configuration update involves the following steps:
Identify the config type to update and note the latest version applied. When a config type is updated the whole property set needs to be updated. So copying the values from the latest and updating specific values or adding/removing properties as needed is the easiest option. Read the cluster resource and note the version of the type you want to update Read the config type with the tag and note the properties Edit the properties as needed and then update the config type
Config update requires creation of a new version (typically current timestamp is a good choice) The new version of the config type must be added and applied to the cluster Restart affected services/components to have the config take effect You can use APIs or a wrapper script (/var/lib/ambari-server/resources/scripts/configs.sh) to edit configurations. Edit configuration using APIs (1.4.1/1.2.5) Verified against releases 1.4.1/1.2.5 Starting 1.4.2/1.4.3 you will have to add -H option to the curl calls. E.g. -H "X-Requested-By: ambari" 1. Find the latest version of the config type that you need to update. curl -u admin:admin -X GET http: //AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME?fields=Clusters/desired_configs
Sample OUTPUT
{
"href" : "http://AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME?fields=Clusters/desired_configs" ,
"Clusters" : {
"cluster_name" : "CLUSTER_NAME" ,
"version" : "HDP-2.0.6" ,
"desired_configs" : {
...
"mapred-site" : {
"user" : "admin" ,
"tag" : "version1384716039631"
}
...
}
}
}
2. Read the config type with correct tag curl -u admin:admin "http://AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME/configurations?type=mapred-site&tag=version1384716039631"
Sample OUTPUT
{
"href" : "http://AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME/configurations?type=mapred-site&tag=version1384716039631" ,
"items" : [
{
"href" : "http://AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME/configurations?type=mapred-site&tag=version1384716039631" ,
"tag" : "version1384716039631" ,
"type" : "mapred-site" ,
"Config" : {
"cluster_name" : "CLUSTER_NAME"
},
"properties" : {
... THESE ARE THE PROPERTY KEY-VALUE PAIRS ...
}
}]
}
3a. Save a new version of the config and apply it (see 3b for doing it using one call) curl --user admin:admin -i -X POST -d '{"type": "mapred-site", "tag": "version1384716041120", "properties" : {"mapreduce.admin.map.child.java.opts" : "-Djava.net.preferIPv4Stack=true -Dhadoop.metrics.log.level=WARN",...}}' http: //AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME/configurations
curl --user admin:admin -i -X PUT -d '{"Clusters":{"desired_config" : {"type": "mapred-site", "tag": "version1384716041120"}}}' http: //AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME
3b. Save a new version of the config and apply it using one call curl --user admin:admin -i -X PUT -d '{"Clusters":{"desired_config" : {"type": "mapred-site", "tag": "version1384716041120", "properties" : {...}}}}' http: //AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME
4. Restart all components or services to have the config change take effect
E.g. Stop and Start a service curl --user admin:admin -i -X PUT -d '{"RequestInfo": {"context": "Stop HDFS"}, "ServiceInfo": {"state": "INSTALLED"}}' http: //AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME/services/HDFS
curl --user admin:admin -i -X PUT -d '{"RequestInfo": {"context": "Start HDFS"}, "ServiceInfo": {"state": "STARTED"}}' http: //AMBARI_SERVER_HOST:8080/api/v1/clusters/CLUSTER_NAME/services/HDFS
... View more
