[
https://issues.apache.org/jira/browse/AMBARI-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated AMBARI-1377:
----------------------------------
Fix Version/s: (was: 1.4.0)
1.4.2
> Add ability to move master components after initial setup
> ---------------------------------------------------------
>
> Key: AMBARI-1377
> URL: https://issues.apache.org/jira/browse/AMBARI-1377
> Project: Ambari
> Issue Type: New Feature
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 1.4.2
>
>
> 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 + HistoryServer
> HBase: MasterServer
> P1. Master Components to Support
> Oozie: Server
> P2. Master Components to Support
> Hive: Metastore
> Hive: HiveServer2
> WebHCat: Server
> P3. Master Components to Support
> Ganglia: Gangalia Collector
> Nagios: Nagios Server
> 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. ( that Ambari doesnt do for him. )
> Step 2: Select the target host. User should be presented with a list of
> possible target hosts in the cluster.
> TODO: Need to determine what it means to be a target. What criteria does that
> host need to meet? Can it be running other master components? Slave
> components? Which ones and/or how many? This answer might be master component
> dependent so need to define this for each of the Master Components listed
> above.
> Step 3: Ask the user to reconfigure the component for this new host. [
> Similar to, each Category Section of Step 7 of Install Wizard ] for example
> select mount points for the new host before reassigning the component.
> 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 was sent by Atlassian JIRA
(v6.1#6144)
