incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-2300) 500 Exception creating service component during install
Date Thu, 06 Jun 2013 14:35:20 GMT
Dmitry Lysnichenko created AMBARI-2300:
------------------------------------------

             Summary: 500 Exception creating service component during install
                 Key: AMBARI-2300
                 URL: https://issues.apache.org/jira/browse/AMBARI-2300
             Project: Ambari
          Issue Type: Bug
          Components: controller
    Affects Versions: 1.2.3
            Reporter: Dmitry Lysnichenko
            Assignee: Dmitry Lysnichenko
             Fix For: 1.2.3


I was installing a new cluster in my VM when the progress blocked on step 12. Looking on browser
log, the PUTs for clusters desired_configs succeeded, but the very next call to create service
component failed.

[POST] http://dev.hortonworks.com:8080/api/v1/clusters/vmc/services?ServiceInfo/service_name=HDFS

Status Code:500 Invalid arguments, clustername and componentname should be non-null and
non-empty when trying to create a component

Data uploaded:
{noformat}
{"components":[{"ServiceComponentInfo":{"component_name":"NAMENODE"}},
{"ServiceComponentInfo":{"component_name":"SECONDARY_NAMENODE"}},
{"ServiceComponentInfo":{"component_name":"DATANODE"}},
{"ServiceComponentInfo":{"component_name":"HDFS_CLIENT"}}]}:
{noformat}


Exception on server console:
{noformat}
Mar 21, 2013 11:25:09 AM com.sun.jersey.spi.container.ContainerResponse mapMappableContainerException
SEVERE: The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
java.lang.IllegalArgumentException: Invalid arguments, clustername and componentname should
be non-null and non-empty when trying to create a component
	at org.apache.ambari.server.controller.AmbariManagementControllerImpl.createComponents(AmbariManagementControllerImpl.java:387)
	at org.apache.ambari.server.controller.internal.ComponentResourceProvider$1.invoke(ComponentResourceProvider.java:88)
	at org.apache.ambari.server.controller.internal.ComponentResourceProvider$1.invoke(ComponentResourceProvider.java:85)
	at org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:229)
	at org.apache.ambari.server.controller.internal.ComponentResourceProvider.createResources(ComponentResourceProvider.java:85)
	at org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:131)
	at org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:75)
	at org.apache.ambari.server.api.handlers.QueryCreateHandler.persist(QueryCreateHandler.java:163)
	at org.apache.ambari.server.api.handlers.QueryCreateHandler.handleRequest(QueryCreateHandler.java:68)
	at org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:98)
	at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:73)
	at org.apache.ambari.server.api.services.ServiceService.createServices(ServiceService.java:114)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)

{noformat}

--
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: http://www.atlassian.com/software/jira

Mime
View raw message