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-12264) Some Execution Commands Send Stale Configs During Upgrade Causing Invalid Alerts
Date Sat, 04 Jul 2015 11:31:12 GMT

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

Hudson commented on AMBARI-12264:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3053 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3053/])
AMBARI-12264 - Some Execution Commands Send Stale Configs During Upgrade Causing Invalid Alerts
(jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9a6d2abbe9537174baee2c5462b0ece807454c61)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* ambari-server/src/test/resources/stacks/HDP/2.2.0/upgrades/upgrade_test.xml
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderHDP22Test.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java


> Some Execution Commands Send Stale Configs During Upgrade Causing Invalid Alerts
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-12264
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12264
>             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
>
>
> During an upgrade, the alert check for hive transitions to the new port, {{10010}} and
begins returning valid checks once the upgraded hive server starts up on the new port. 
> However, after the upgrade is finalized, it is observed that the configurations sent
down to the agents contains the old hive thrift port, {{10000}} from before the upgrade ran.

> Restarting the agents corrects the problems since the configurations in ambari server
are still correct.
> The problem is that some commands, namely, {{ACTIONEXECUTE}} must also set
> - {code}
>     "forceRefreshConfigTagsBeforeExecution": [
>         "*"
>     ],
> {code}
> on the {{ExecutionCommands}} being sent down.



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

Mime
View raw message