[ 
https://issues.apache.org/jira/browse/AMBARI-21868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150433#comment-16150433
 ] 

Hadoop QA commented on AMBARI-21868:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12884923/AMBARI-21868.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:red}-1 core tests{color}.  The test build failed in 
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12135//artifact/patch-work/testrun_ambari-server.txt]
 

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12135//console

This message is automatically generated.

> Allow state transition from INSTALLED to INIT for host recovery
> ---------------------------------------------------------------
>
>                 Key: AMBARI-21868
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21868
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21868.patch
>
>
> *Problem Statement*:
> Allow user to bring back a host/VM that is dead with the same hostname and 
> allow an action to recover the state of the host to what it was before the 
> incident
> *Solution*:
> - User gets the host/VM back with same hostname (different IP address is ok)
> - The UI state would be INSTALLED for all host components as soon as the host 
> starts heart beating
> - User will initiate a Recover user action that will do the following (batch 
> operation):
> -- Move the state of the components back to INIT (allow this state transition)
> {code}
> curl -H "X-Requested-By:ambari" -u admin:admin -i -X PUT -d 
> {"RequestInfo":{"context":"Reset All Host 
> Components","operation_level":{"level":"HOST","cluster_name":"c1","host_names":"c6401.ambari.apahe.org"},"query":"HostRoles/component_name.in(DATANODE,NODEMANAGER,METRICS_MONITOR)"},"Body":{"HostRoles":{"state":"INIT"}}}
>  
> http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/hosts/c6401.ambari.apache.org/host_components
> {code}
> -- Issue an INSTALL operation on all hostcomponents (Same call as above with 
> state = "INSTALLED")
> -- Issue a START operation on all hostcomponents (Same call as above with 
> state = "STARTED")
> *Note*: The above operation is expected to recover the security state of the 
> host.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to