You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Babiichuk (JIRA)" <ji...@apache.org> on 2015/06/19 12:53:00 UTC

[jira] [Created] (AMBARI-12016) Going over maximum in config-group shows errors in default-config-group

Andrii Babiichuk created AMBARI-12016:
-----------------------------------------

             Summary: Going over maximum in config-group shows errors in default-config-group
                 Key: AMBARI-12016
                 URL: https://issues.apache.org/jira/browse/AMBARI-12016
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.1.0
            Reporter: Andrii Babiichuk
            Assignee: Andrii Babiichuk
            Priority: Critical
             Fix For: 2.1.0


# Installed a brand new cluster
# Went to YARN service and created a new config-group with 1 host.
# Selected the config-group and overrode {{yarn.nodemanager.resource.memory-mb}} and moved the value from 2048 to 2304.
# Because of above step {{yarn.scheduler.maximum-allocation-mb}} also moved to 2304, but was shown as an error (even when API bumped up maximum to 2304). *Problem 1*
# Saved the config-group - hit a blank page.
# Went back to default-config-group.
# Reloaded page
# *Problem 2* - The overridden value for new config-group is still shown as 2048 when it should have been 2304.



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