[
https://issues.apache.org/jira/browse/AMBARI-18034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409066#comment-15409066
]
Hadoop QA commented on AMBARI-18034:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12822259/AMBARI-18034.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8304//console
This message is automatically generated.
> 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
> 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)
