You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Di Li (JIRA)" <ji...@apache.org> on 2015/09/23 23:23:04 UTC

[jira] [Commented] (AMBARI-12823) RU: Yarn Capacity Scheduler view is not available on the Ambari web UI after the rolling upgrade

    [ https://issues.apache.org/jira/browse/AMBARI-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905286#comment-14905286 ] 

Di Li commented on AMBARI-12823:
--------------------------------

Users can create Capacity scheduler view instances on the Ambari web UI once the upgrade is finalized.
the rolling upgrade wizard could display some text at the finalize step to remind users of they having options to create instances via Ambari web UI.

> RU: Yarn Capacity Scheduler view is not available on the Ambari web UI after the rolling upgrade
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12823
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12823
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server, ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Di Li
>            Priority: Critical
>
> Yarn Capacity scheduler view is not available post rolling upgrade, as the viewinstance table does not contain the capacity scheduler as a row.
> This seems to because the capacity scheduler is set to AUTO-CS-INSTANCE instead of instance like the Admin_View. rolling upgrade doesn't update the database with those auto-cs-instance view jars. 
> Per logic in ViewRegistry.java, readViewArchive method, persistView method, only views with instance defined in the view.xml gets instances added into the viewinstance table.



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