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-9420) Configure Upgrade Task Needs to be More Flexible
Date Mon, 02 Feb 2015 19:18:36 GMT

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

Hudson commented on AMBARI-9420:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #1663 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1663/])
AMBARI-9420 - Configure Upgrade Task Needs to be More Flexible (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=91ff07e16e828c0471e00bf3a7ba3b6bb8fc5445)
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterDeadlockTest.java
* ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/ConfigureAction.java
* ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test.xml
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ConfigureTask.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java


> Configure Upgrade Task Needs to be More Flexible
> ------------------------------------------------
>
>                 Key: AMBARI-9420
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9420
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9420.patch
>
>
> Consider the issue described in BUG-30470, where Hive's configure task has different
behavior based on an aspect of the system. As a result, the configure task should allow additional
elements/attributes that govern what to change and when.
> An example of this might be
> {code}
> <task xsi:type="configure">
>   <condition>
>       <property>hive.server2.transport.mode<property/>
>       <value>http</value>
>       <type>hive-site</type>
>       <key>hive.server2.http.port</key>
>       <value>10011</value>      
>   <condition>
>   <condition>
>       <property>hive.server2.transport.mode<property/>
>       <value>binary</value>
>       <type>hive-site</type>
>       <key>hive.server2.thrift.port</key>
>       <value>10010</value>      
>   <condition>
> </task>
> {code}
> Additionally, there can be more specific configure tasks as well. Such as a port configuration
task which knows to adjust the port by 10 beyond the current value.
> Existing configure tasks in the upgrade XML should be evaluated to determine what the
requirements are to allow for a more flexible upgrade script.



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

Mime
View raw message