ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-5133) Maintenance Mode: On Host Details page, Start All fails
Date Tue, 18 Mar 2014 23:40:45 GMT
Jaimin D Jetly created AMBARI-5133:
--------------------------------------

             Summary: Maintenance Mode: On Host Details page, Start All fails
                 Key: AMBARI-5133
                 URL: https://issues.apache.org/jira/browse/AMBARI-5133
             Project: Ambari
          Issue Type: Bug
          Components: client
    Affects Versions: 1.5.0
            Reporter: Jaimin D Jetly
            Assignee: Jaimin D Jetly
             Fix For: 1.5.0


This happens as FE includes client components while issuing start all host components call
and client does not have STARTED as desired state.

{noformat}
Request:
URL:http://162.216.149.63:8080/api/v1/clusters/mirror1/hosts/yusakum1-3.c.pramod-thangali.internal/host_components

Form Data:
{"RequestInfo":{"context":"Start All Host Components","query":"HostRoles/component_name.in(DATANODE,FALCON_CLIENT,GANGLIA_MONITOR,HBASE_CLIENT,HBASE_REGIONSERVER,HCAT,HDFS_CLIENT,HIVE_CLIENT,MAPREDUCE2_CLIENT,NODEMANAGER,OOZIE_CLIENT,PIG,SQOOP,SUPERVISOR,TEZ_CLIENT,YARN_CLIENT,ZOOKEEPER_CLIENT,ZOOKEEPER_SERVER)"},"Body":{"HostRoles":{"state":"STARTED"}}}

Response:
{
  "status" : 400,
  "message" : "java.lang.IllegalArgumentException: Invalid desired state for a client component"
}
{noformat}

*Note:*  "Stop All" call should not have client components, either.
We need to make sure that the client components are included for "Restart All" call.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message