ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laszlo Puskas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17251) Client components that are dependencies of services in the stack definitions are always added to blueprint deployments
Date Wed, 15 Jun 2016 12:04:09 GMT

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

Laszlo Puskas updated AMBARI-17251:
-----------------------------------
    Summary: Client components that are dependencies of services in the stack definitions
are always added to blueprint deployments  (was: SPARK_CLIENT/TEZ_CLIENT should not be auto
deployed as part of YARN ATS)

> Client components that are dependencies of services in the stack definitions are always
added to blueprint deployments
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17251
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17251
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>             Fix For: 2.4.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Problem:
> Component dependencies from stack definitions are automatically added to blueprint deployments
even the services components belong to are not listed in the blueprint.
> eg. SPARK_CLIENT/TEZ_CLIENT components that are listed as dependencies of the ATS and
RESOURCEMANAGER in the stack definitions are always added to blueprints.



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

Mime
View raw message