ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <>
Subject [jira] [Created] (AMBARI-1513) Add ability to re-assign master components to different host after installation
Date Wed, 27 Feb 2013 19:21:12 GMT
Jeff Sposetti created AMBARI-1513:

             Summary: Add ability to re-assign master components to different host after installation
                 Key: AMBARI-1513
             Project: Ambari
          Issue Type: Improvement
            Reporter: Jeff Sposetti

Provide ability to move master components of services to different host after installation.
For example, move HDFS NameNode to a different host in the cluster after the install or at
some later date etc, etc.

This is the list of Master Components to support re-assign, grouped by priority order.

P0. Master Components to Support

HDFS: NameNode
HDFS: SecondaryNameNode
MapReduce: JobTracker
HBase: MasterServer

P1. Master Components to Support

Hive: Metastore
Hive: HiveServer2
WebHCat: Server

P2. Master Components to Support

Hue: Hue Server
Oozie: Server

P3. Master Components to Support

Ganglia: Gangalia Collector
Nagios: Nagios Server

Suggested Flow

* Support moving a single master component at a time. For example: Services > HDFS, under
the "Maintenance" dropdown, add options "Reassign NameNode" and "Reassign SNameNode"
* After selecting the option, popup wizard walks user through the re-assign

Step 1: List all the manual steps
That the user must explicitly do after Step 2 (i.e. what Ambari does not perform).

Step 2: Select the target host 
User should be presented with a list of possible target hosts in the cluster.

Step 3: Ask the user to reconfigure the component for this new host.
For example select mount points for the new host before reassigning the component (Similar
to each Category Section of Step 7)

Step 4: Ask user to confirm.

Step 5: Show the order and state of tasks with live update. For example, stopping services,
installing component on target host, applying config, adjusting cluster settings for new master
host, restarting services, removing old master component (from source host).

Step 6: Complete.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message