ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-11358) During RU, capacity scheduler config needs to be modified for HDP-2.3 to get rid of bad values
Date Sat, 23 May 2015 01:13:17 GMT
Jonathan Hurley created AMBARI-11358:
----------------------------------------

             Summary: During RU, capacity scheduler config needs to be modified for HDP-2.3
to get rid of bad values
                 Key: AMBARI-11358
                 URL: https://issues.apache.org/jira/browse/AMBARI-11358
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Blocker
             Fix For: 2.1.0


The following three config properties should be removed if the values are the HDP-2.2 default.

* yarn.scheduler.capacity.root.accessible-node-labels.default.capacity
** Remove if value is "-1"
* yarn.scheduler.capacity.root.accessible-node-labels.default.maximum-capacity
** Remove if value is "-1"
* yarn.scheduler.capacity.root.default-node-label-expression
** Remove if value is " " (space)

There is currently no logic in place that says remove a property if the property meets a condition.
That would require work. Some options:

- We have the ability to set a property if a property meets a condition. For example, we can
set {{yarn.scheduler.capacity.root.accessible-node-labels.default.capacity}} to {{""}} or
{{10}} if it is currently {{-1}}
- We can just set it regardless of any condition to any value
- We can just remove it outright
- We can write a pre-req check and have the user change it.

The best balance of effort/reward is option #1 - conditionally set the properties.



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

Mime
View raw message