You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2014/01/03 16:54:50 UTC
[jira] [Created] (AMBARI-4223) Cluster topology is hard-coded
Nate Cole created AMBARI-4223:
---------------------------------
Summary: Cluster topology is hard-coded
Key: AMBARI-4223
URL: https://issues.apache.org/jira/browse/AMBARI-4223
Project: Ambari
Issue Type: Task
Components: controller
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 1.5.0
The cluster topology is passed to agents during setup and configuration. This happens via {{StageUtils}} using a static map like so:
{code}
componentToClusterInfoKeyMap.put("NAMENODE", "namenode_host");
componentToClusterInfoKeyMap.put("JOBTRACKER", "jtnode_host");
componentToClusterInfoKeyMap.put("SNAMENODE", "snamenode_host");
componentToClusterInfoKeyMap.put("RESOURCEMANAGER", "rm_host");
{code}
At runtime, we determine the hosts for each role, and pass them down. When wiring up new services, any role missing from this map will not be sent to the agent, when that information may be required.
Proposal is to maintain this map for backwards compatibility, and pass any undefined master/slave components as "<rolename>_hosts" Client topology need not be passed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)