Andrew Onischuk created AMBARI-6555:
---------------------------------------
Summary: Stack API: Incorrect information from cardinality field
of service component.
Key: AMBARI-6555
URL: https://issues.apache.org/jira/browse/AMBARI-6555
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
**Case 1: MYSQL_SERVER**
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/stacks/HDP/versions/2.1/services/HIVE/components/MYSQL_SERVER?fields=StackServiceComponents/cardinality";,
"StackServiceComponents" : {
"cardinality" : "1",
"component_name" : "MYSQL_SERVER",
"service_name" : "HIVE",
"stack_name" : "HDP",
"stack_version" : "2.1"
}
}
It's possible to provision a cluster without creating MYSQL_SERVER component
when we choose existing databases. Cardinality field for MYSQL_SERVER should
be [0,1] in interval notation (at the most 1)
**Case 2: ATS**
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/stacks/HDP/versions/2.1/services/YARN/components/APP_TIMELINE_SERVER?fields=StackServiceComponents/cardinality";,
"StackServiceComponents" : {
"cardinality" : "1",
"component_name" : "APP_TIMELINE_SERVER",
"service_name" : "YARN",
"stack_name" : "HDP",
"stack_version" : "2.1"
}
}
It's possible to provision a cluster without creating ATS host component.
Ambari kerberized cluster does not have ATS host component. Cardinality field
for ATS should be [0,1] (at the most 1)
**Case 3: Hbase Master**
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/stacks/HDP/versions/2.1/services/HBASE/components/HBASE_MASTER?fields=StackServiceComponents/cardinality";,
"StackServiceComponents" : {
"cardinality" : "1",
"component_name" : "HBASE_MASTER",
"service_name" : "HBASE",
"stack_name" : "HDP",
"stack_version" : "2.1"
}
}
It's possible to provision a cluster with more than 1 HBase Master. Even
Ambari-web client's installer wizard supports provisioning a cluster with
multiple HBase Master host component.
Cardinality field for HBASE_MASTER should be 1+.
**Case 4: NameNode:**
{
"href" :
"http://c6401.ambari.apache.org:8080/api/v1/stacks/HDP/versions/2.1/services/HDFS/components/NAMENODE?fields=StackServiceComponents/cardinality";,
"StackServiceComponents" : {
"cardinality" : "1",
"component_name" : "NAMENODE",
"service_name" : "HDFS",
"stack_name" : "HDP",
"stack_version" : "2.1"
}
}
It's possible to provision a cluster with multiple NameNode hostComponent and
Cardinality field for NameNode should be [1,2].
**Case 5: ResourceManager:**
We are supporting ResourceManager HA and Cardinality field for ResourceManager
should be [1,2].
**Case 6: All Clients:**
cardinality of client component is 0+. Ambari does not support a service with
no client component of a service installed in a cluster. Ambari needs client
component as service check task for every service is executed via service
client. Cardinality of all client components should be **1+**
--
This message was sent by Atlassian JIRA
(v6.2#6252)
