Apache Ambari BOF - Configs - Hadoop Summit 2013
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Apache Ambari BOF - Configs - Hadoop Summit 2013

  • 1,376 views
Uploaded on

Apache Ambari BOF Meet Up @ Hadoop Summit 2013 ...

Apache Ambari BOF Meet Up @ Hadoop Summit 2013

Configs

http://www.meetup.com/Apache-Ambari-User-Group/events/119184782/

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,376
On Slideshare
1,376
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
33
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. © Hortonworks Inc. 2013 Ambari Configuration API June 25, 2013 Page 1
  • 2. © Hortonworks Inc. 2013 Agenda • Purpose • Types • Cluster • Host Overrides • Host Component / Actual Page 2
  • 3. © Hortonworks Inc. 2013 Purpose • Provide ability to set any config parameter • Values used to populate configuration files in /etc/hadoop/conf (core-site, hdfs-site, etc) • Mechanism to set and view configurations • Insight into host configuration state Page 3
  • 4. © Hortonworks Inc. 2013 Types • Two main types: global and site • Global Configuration –Values required by shell or puppet scripts –Denoted using specially named global type • Site-specific Configurations –Used by Hadoop components for fine-tuning a cluster –Named using standard Hadoop types (core-site, hdfs-site, mapred-site, etc) Page 4
  • 5. © Hortonworks Inc. 2013 Cluster - Definition • All configurations stored with cluster GET /api/v1/clusters/c1/configurations?type=global&tag=version1 { "type": "global", "tag": "version1", "properties": { "a": "b", "c": "d" } } • Uniqueness defined by type/tag combinations • Type is matched to Hadoop configuration names, but is not restricted • Tag can be any string Page 5
  • 6. © Hortonworks Inc. 2013 Cluster – Desired • Only One Desired per type GET /api/v1/clusters/c1 { "Clusters": { "cluster_id": 1, "desired_configs": { "global": { "tag": "version1", "user": "admin" }, ... } } } • Auditing username and timestamp Page 6
  • 7. © Hortonworks Inc. 2013 Host Overrides – Desired • Mechanism to set specific host-level overrides • Only One Desired per type, like Cluster GET /api/v1/clusters/c1/hosts/h1 { "Hosts": { "cluster_name": "c1", "host_name": "h1", "desired_configs": { "global": { "tag": "custom-mapred", "user": "admin" }, ... } } } Page 7
  • 8. © Hortonworks Inc. 2013 Host Components – Actual • Discreet information, per Host Component • Structure similar to Cluster/Host desired GET /api/v1/clusters/c1/hosts/h1/host_components/DATANODE { "HostRoles" : { "cluster_name" : "c1", "component_name" : "DATANODE", "actual_configs" : { "core-site" : { "tag" : "version1" }, "global" : { "tag" : "version1” } } } } Page 8
  • 9. © Hortonworks Inc. 2013 Thank You Page 9