[
https://issues.apache.org/jira/browse/AMBARI-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968551#comment-14968551
]
Hadoop QA commented on AMBARI-13507:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12767825/AMBARI-13507.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4031//console
This message is automatically generated.
> Create a script to change host names for a stopped cluster
> ----------------------------------------------------------
>
> Key: AMBARI-13507
> URL: https://issues.apache.org/jira/browse/AMBARI-13507
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.1.3
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13507.patch
>
>
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are
> stopped)
> We may also need to check and confirm that there are no commands pending
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g.
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade
> code
> Modify all configs to replace the hostnames as needed (not sure if plain
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
