[AMBARI-9778] In cluster layout recommendation, slave component cardinality of 0+ not being used

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 24/Feb/15 19:21
• Updated: 25/Apr/18 12:01
• Resolved: 25/Feb/15 12:13

Description

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.

Issue Links

• relates to: AMBARI-23684 Deselect NFS Gateway (and Phoenix Query Server) by default in Ambari UI deployment
• links to: ReviewBoard