ambari-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/AMBARI-18034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-18034:
----------------------------------------
    Resolution: Fixed
      Assignee: Dmitry Lysnichenko
        Status: Resolved  (was: Patch Available)

Committed
   d08da2d..7d2df9f  branch-2.4 -> branch-2.4
   dc07222..2b7c97f  trunk -> trunk


> 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