[
https://issues.apache.org/jira/browse/AMBARI-17970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401606#comment-15401606
]
Hudson commented on AMBARI-17970:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5425 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5425/])
AMBARI-17970 - Ambari Sends Cached Configurations On Initial Task (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ecc19031952bf37829f07752f0563acb0eab52df])
*
ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterDAO.java
*
ambari-server/src/main/java/org/apache/ambari/server/events/publishers/JPAEventPublisher.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/ActionManagerTestHelper.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionDBAccessorImpl.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionSchedulerThreading.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionManager.java
*
ambari-server/src/main/java/org/apache/ambari/server/events/jpa/EntityManagerCacheInvalidationEvent.java
*
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
* ambari-server/src/main/java/org/apache/ambari/server/events/jpa/JPAEvent.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
*
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatProcessorTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatTestHelper.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java
> Ambari Sends Cached Configurations On Initial Task Execution Attempt
> --------------------------------------------------------------------
>
> Key: AMBARI-17970
> URL: https://issues.apache.org/jira/browse/AMBARI-17970
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17970.patch
>
>
> - Install Ambari with HDP 2.4 and Ranger
> - Perform a rolling upgrade HDP 2.5, but don't finalize
> - Start a downgrade
> The first command when a downgrade starts is the restart command for Ranger
> Admin. The daemon is currently running on HDP 2.5, however the restart
> command which is sent must be for HDP 2.4 as it will have the 2.4
> configurations to write out.
> The command fails with:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py",
> line 199, in <module>
> RangerAdmin().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 685, in restart
> self.stop(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py",
> line 60, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/RANGER/0.4.0/package/scripts/params.py",
> line 178, in <module>
> audit_jdbc_url =
> format('jdbc:postgresql://{db_host}/{ranger_auditdb_name}') if
> stack_supports_ranger_audit_db else None
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/format.py",
> ...
> packages/resource_management/libraries/script/config_dictionary.py", line 73,
> in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'audit_db_name' was not found in configurations dictionary!
> {code}
> The {{audit_db_name}} parameter was removed from Ranger in HDP 2.5. On the
> downgrade restart command, we are supposed to be sending HDP 2.4
> configurations. However, {{audit_db_name}} is missing.
> Well, it looks like what we have here is an EclipseLink caching problem.
> Essentually, at time index {{15:47:22,172}}, thread
> {{ambari-action-scheduler}} gets the wrong desired configs from the entities
> that JPA has cached for it. However, a mere second later at {{15:47:23,258}},
> it has the right ones.
> It's the first second that is so critical; {{ambari-client-thread-74}}
> updates the entities and can see the correct data immediately. But it takes
> {{ambari-action-scheduler}} a second or so to see them.
> {code}
> 2016-07-29 15:47:21,917 INFO [ambari-client-thread-74]
> (ClusterImpl.java:3347) applyLatestConfigurations() - Applied latest
> configurations for c1 on stack HDP-2.4. The desired configurations are now
> {zookeeper-env={tag=TOPOLOGY_RESOLVED},
> zookeeper-log4j={tag=TOPOLOGY_RESOLVED}, cluster-env={tag=TOPOLOGY_RESOLVED},
> zoo.cfg={tag=TOPOLOGY_RESOLVED}}
> 2016-07-29 15:47:22,172 INFO [ambari-action-scheduler]
> (ExecutionCommandWrapper.java:131) getExecutionCommand() - While scheduling
> task 102 on cluster c1, configurations are being refreshed using desired
> configurations of {zookeeper-env={tag=version1469808399092},
> zookeeper-log4j={tag=version1469808399069},
> cluster-env={tag=version1469808399109}, zoo.cfg={tag=version1469808399131}}
> 2016-07-29 15:47:23,258 INFO [ambari-action-scheduler]
> (ExecutionCommandWrapper.java:131) getExecutionCommand() - While scheduling
> task 102 on cluster c1, configurations are being refreshed using desired
> configurations of {zookeeper-env={tag=TOPOLOGY_RESOLVED},
> zookeeper-log4j={tag=TOPOLOGY_RESOLVED}, cluster-env={tag=TOPOLOGY_RESOLVED},
> zoo.cfg={tag=TOPOLOGY_RESOLVED}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
