ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7279) Config History: capacity-scheduler properties from service_config_version should be in same order as before
Date Fri, 12 Sep 2014 15:20:33 GMT

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

Hudson commented on AMBARI-7279:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #230 (See [https://builds.apache.org/job/Ambari-trunk-Commit/230/])
AMBARI-7279 Config History: capacity-scheduler properties from service_config_version should
be in same order as before (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ae4801519645b960f66fd6a97a5f4819f9ee2a89)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceConfigVersionResourceProvider.java


> Config History: capacity-scheduler properties from service_config_version should be in
same order as before
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7279
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7279
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 1.7.0
>
>
> From API {code}http://c6401.ambari.apache.org:8080/api/v1/clusters/c123/configurations/service_config_versions?service_name=YARN&service_config_version=8{code}
> The capacity-scheduler properties are: 
> {code}"Config" : {
>             "cluster_name" : "c123"
>           },
>           "type" : "capacity-scheduler",
>           "tag" : "version1409783371662",
>           "version" : 2,
>           "properties" : {
>             "yarn.scheduler.capacity.root.default.acl_administer_jobs" : "*",
>             "yarn.scheduler.capacity.root.queues" : "default",
>             "yarn.scheduler.capacity.node-locality-delay" : "40",
>             "yarn.scheduler.capacity.root.default.maximum-capacity" : "100",
>             "yarn.scheduler.capacity.maximum-am-resource-percent" : "0.2",
>             "yarn.scheduler.capacity.root.default.acl_submit_applications" : "*",
>             "yarn.scheduler.capacity.root.default.state" : "RUNNING",
>             "yarn.scheduler.capacity.root.acl_administer_queue" : "*",
>             "yarn.scheduler.capacity.maximum-applications" : "10006",
>             "yarn.scheduler.capacity.root.default.capacity" : "100",
>             "yarn.scheduler.capacity.root.default.user-limit-factor" : "1",
>             "yarn.scheduler.capacity.root.capacity" : "100"
>           },
>           "properties_attributes" : { }
> {code}
> However, the properties we get from {code}http://c6401.ambari.apache.org:8080/api/v1/clusters/c123/configurations?type=capacity-scheduler&tag=version1409783371662{code}
> are:
> {code}
> "href" : "http://c6401.ambari.apache.org:8080/api/v1/clusters/c123/configurations?type=capacity-scheduler&tag=version1409783371662",
>       "tag" : "version1409783371662",
>       "type" : "capacity-scheduler",
>       "version" : 2,
>       "Config" : {
>         "cluster_name" : "c123"
>       },
>       "properties" : {
>         "yarn.scheduler.capacity.maximum-am-resource-percent" : "0.2",
>         "yarn.scheduler.capacity.maximum-applications" : "10006",
>         "yarn.scheduler.capacity.node-locality-delay" : "40",
>         "yarn.scheduler.capacity.root.acl_administer_queue" : "*",
>         "yarn.scheduler.capacity.root.capacity" : "100",
>         "yarn.scheduler.capacity.root.default.acl_administer_jobs" : "*",
>         "yarn.scheduler.capacity.root.default.acl_submit_applications" : "*",
>         "yarn.scheduler.capacity.root.default.capacity" : "100",
>         "yarn.scheduler.capacity.root.default.maximum-capacity" : "100",
>         "yarn.scheduler.capacity.root.default.state" : "RUNNING",
>         "yarn.scheduler.capacity.root.default.user-limit-factor" : "1",
>         "yarn.scheduler.capacity.root.queues" : "default"
>       }
> {code}
> Notice that the order of properties are different though the property values are the
same.
> This issue will a FE issue as attached. 
> (the light blue highlight meaning, in current compare view, capacity-scheduler are different
in the two versions. However, each value is the same, the only difference is the sorting of
properties.)
> Expected results:
> from {code}/configurations/service_config_versions?service_name=YARN&service_config_version=8{code},
we should get the properties in the same order as {code}/configurations?type=capacity-scheduler&tag=version14..{code}



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

Mime
View raw message