[
https://issues.apache.org/jira/browse/AMBARI-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652049#comment-14652049
]
Hudson commented on AMBARI-12595:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #310 (See
[https://builds.apache.org/job/Ambari-branch-2.1/310/])
AMBARI-12595. Blueprint deployments should refresh configuration on all
commands. (rnettleton) (rnettleton:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d03bc09e41e30b4f108ad83b9b239d7bf9d140bd)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
> Blueprint deployments should refresh configuration on all commands
> ------------------------------------------------------------------
>
> Key: AMBARI-12595
> URL: https://issues.apache.org/jira/browse/AMBARI-12595
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12595.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> During Blueprint deployments of large clusters, there are intermittent
> failures where configuration appears to not be sychronized with the rest of
> the cluster. This can cause un-resolved configuration to be sent down to a
> node, and this will subsequently cause install and start failures.
> When a Blueprint deployment is in process, the AmbariManagementController
> implementation should force a refresh on the config if each ExecutionCommand
> prior to sending it down to the cluster nodes.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
