You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Gaurav Nagar (JIRA)" <ji...@apache.org> on 2016/05/06 16:47:12 UTC
[jira] [Updated] (AMBARI-16289) Upgrade existing capacity scheduler
view instance after the Remote Ambari Cluster changes
[ https://issues.apache.org/jira/browse/AMBARI-16289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gaurav Nagar updated AMBARI-16289:
----------------------------------
Description:
With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler instances which is configured as Custom won't work.
We need to provide proper upgrade for those instances, so instances will work without any extra configuration after upgrade
was:
With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler instances which is configured as Custom won't work.
We need to provide proper upgrade for those instances, so instances will work without any extra configuration.
> Upgrade existing capacity scheduler view instance after the Remote Ambari Cluster changes
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-16289
> URL: https://issues.apache.org/jira/browse/AMBARI-16289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Reporter: Gaurav Nagar
> Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
>
> With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler instances which is configured as Custom won't work.
> We need to provide proper upgrade for those instances, so instances will work without any extra configuration after upgrade
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)