You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Di Li (JIRA)" <ji...@apache.org> on 2017/02/02 16:01:51 UTC

[jira] [Resolved] (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:all-tabpanel ]

Di Li resolved AMBARI-12823.
----------------------------
    Resolution: Cannot Reproduce

close it now as I can't reproduce it in Ambari 2.4.2 anymore.

> 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.15#6346)