Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-9778

In cluster layout recommendation, slave component cardinality of 0+ not being used

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.1.0
    • None
    • None

    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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            aonishuk Andrew Onischuk
            aonishuk Andrew Onischuk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment