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] [Updated] (AMBARI-7301) Remove the ambri-web logic around stack version number
Date Mon, 15 Sep 2014 04:59:33 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jaimin D Jetly updated AMBARI-7301:
-----------------------------------
    Description: 
Cardinality field can imply number of allowable service components in the cluster.
If any master components has a static number greater than 1 (For example: 2), then we can
infer that it supports high availability
Although for other features (example: kerberos security, move master, metrics, alerts support)
that are independent of any information provided in stack, I agree that Nate Cole proposal
(done offline) of having feature will be helpful in such scenarios.


> Remove the ambri-web logic around stack version number
> ------------------------------------------------------
>
>                 Key: AMBARI-7301
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7301
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 1.7.0
>
>
> Cardinality field can imply number of allowable service components in the cluster.
> If any master components has a static number greater than 1 (For example: 2), then we
can infer that it supports high availability
> Although for other features (example: kerberos security, move master, metrics, alerts
support) that are independent of any information provided in stack, I agree that Nate Cole
proposal (done offline) of having feature will be helpful in such scenarios.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message