You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2014/08/06 18:21:14 UTC

[jira] [Resolved] (AMBARI-6755) ATS is marked as slave component but appears on Assign Master Page on web-ui.

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

Vitaly Brodetskyi resolved AMBARI-6755.
---------------------------------------

    Resolution: Fixed

Committed to trunk

> ATS is marked as slave component but appears on Assign Master Page on web-ui.
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-6755
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6755
>             Project: Ambari
>          Issue Type: Task
>          Components: agent
>    Affects Versions: 1.6.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6755.patch
>
>
> At some point, we marked ATS as slave component instead of master component in the API. This seems incorrect. UI needs to have special cases to make this slave component appear as master on web-ui. Rather we should mark ATS as master.
> If we want the unavailability of ATS in secure mode should not affect yarn health status then we should have another fix addressing it specifically but marking ATS as slave component in the API does not seem right.



--
This message was sent by Atlassian JIRA
(v6.2#6252)