[
https://issues.apache.org/jira/browse/AMBARI-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-12823:
---------------------------
Description:
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.
was:
Yarn Capacity scheduler view is not available post rolling upgrade, as the
viewinstance table does not contain the capacity scheduler record.
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.
> 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
> Affects Versions: 2.1.0
> Reporter: Di Li
>
> 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)
