ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doroszlai, Attila (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-22244) Update service component API call to work for second service instance
Date Mon, 16 Oct 2017 15:29:00 GMT
Doroszlai, Attila created AMBARI-22244:
------------------------------------------

             Summary: Update service component API call to work for second service instance
                 Key: AMBARI-22244
                 URL: https://issues.apache.org/jira/browse/AMBARI-22244
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 3.0.0
            Reporter: Doroszlai, Attila
            Assignee: Doroszlai, Attila
             Fix For: 3.0.0


*Background:*
AMBARI-21824 & AMBARI-22164 moved service API to {{/api/v1/clusters/<cluster-name>/servicegroups/<service-group-name>/services}}.
The service API was also updated to be able to create a second service instance.

{code}
POST /api/v1/clusters/cl1/servicegroups/core/services
{
  "ServiceInfo" : {
    "service_name": "ZK2",
    "service_type": "ZOOKEEPER"
  }
}
{code}
In the example above {{service_name = ZK2}} is the user-defined service name and {{service_type
= ZOOKEEPER}} is the actual service name as defined in the stack definition. 

*Issue:*
# There are issues with creating a service component for the second instance (i.e. {{POST
/api/v1/clusters/cl1/servicegroups/core/services/ZK2/components/ZOOKEEPER_SERVER}} etc can
cause failures). 
# This is primarily because there are code blocks where we use {{service_name}} instead of
{{service_type}} to make calls to {{ambariMetaInfo.getService(stackName, stackVersion, stackServiceName)}}.

# So we end up making a call {{ambariMetaInfo.getService("HDP", "3.0.0", "ZK1")}}. We need
to fix issues like these to be able to make our APIs multi-instance ready.



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

Mime
View raw message