ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-9778) In cluster layout recommendation, slave component cardinality of 0+ not being used
Date Wed, 25 Feb 2015 12:14:04 GMT

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

Andrew Onischuk resolved AMBARI-9778.
-------------------------------------
    Resolution: Fixed

Committed to trunk

> In cluster layout recommendation, slave component cardinality of 0+ not being used
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-9778
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9778
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.0
>
>
> We now have a slave component that has a cardinality of `0+`. This component
> in UI install wizard's host selection page does not want to be selected unless
> the user specifically checks hosts. Upto now we have not used cardinality to
> determine slave-component layout.
> This should change so that when slave-component layout is being determined, it
> should ask if component-name should use cardinality for layout. Call this
> method `isComponentUsingCardinalityForLayout(componentName)`. The default-
> stack-advisor will have always return false. However some stack-version could
> return true. If so, the minimum number in the cardinality will determine the
> number of hosts for the slave-component. If it is `0+`, then 0 hosts will be
> selected. If it is `1+`, then atleast 1 host will be selected.



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

Mime
View raw message