[
https://issues.apache.org/jira/browse/AMBARI-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660431#comment-14660431
]
Hudson commented on AMBARI-12652:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3238 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3238/])
AMBARI-12652. Repeated debug log during Blueprint deployment should not be
present by default. (rnettleton) (rnettleton:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=422c6e1202d013a1873a14f000814fa582306cf4)
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
> Repeated debug log during Blueprint deployment should not be present by
> default
> -------------------------------------------------------------------------------
>
> Key: AMBARI-12652
> URL: https://issues.apache.org/jira/browse/AMBARI-12652
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 2.1.1
>
> Attachments: AMBARI-12652.patch
>
>
> During a Blueprint deployment, the following log message appears repeatedly:
> {code}
> ExecutionCommandWrapper:109 - ExecutionCommandWrapper.getExecutionCommand:
> refreshConfigTag set to *, so clearing config for full refresh.
> {code}
> This log message is useful for debugging deployment failures in large
> clusters, but should not be present in the log by default, as this message
> repeats often enough to make debugging normal conditions less simple.
> This log message is currently logged at the INFO level, but should be changed
> to log at the DEBUG level.
> 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)
