ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18034) Issues with custom default queue support
Date Fri, 05 Aug 2016 19:33:20 GMT

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

Hudson commented on AMBARI-18034:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5466 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5466/])
AMBARI-18034. Issues with custom default queue support (dgrinenko via (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2b7c97fc19a57bb28e8d850242d573fdf1915174])
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* ambari-server/src/main/resources/common-services/SPARK/1.5.2/configuration/spark-thrift-sparkconf.xml
* ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-thrift-sparkconf.xml
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* ambari-server/src/main/resources/common-services/SPARK/1.2.1/configuration/spark-defaults.xml
* ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-defaults.xml
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/webhcat-site.xml


> Issues with custom default queue support
> ----------------------------------------
>
>                 Key: AMBARI-18034
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18034
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Grinenko
>            Assignee: Dmitry Lysnichenko
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-18034.patch
>
>
> While investigating config changes due to Ambari upgrade discovered few potential issues
around the support for default custom queue.
> # Ambari upgrade should not update custom queue properties. This is because its unlikely
to be invalid before Ambari upgrade.
> # All config properties related to the queue should be marked to not be added during
ambari upgrade. They all have defaults as "default"
> # Stack advisor should recommend only if the existing value for the queue is invalid.
Think of a scenario where user has explicitly set "spark.yarn.queue"/"tez.queue.name" with
a valid value and capacity scheduler goes through an unrelated  config change



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

Mime
View raw message