[
https://issues.apache.org/jira/browse/AMBARI-19372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799903#comment-15799903
]
Hadoop QA commented on AMBARI-19372:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845634/AMBARI-19372.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-agent
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9902//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9902//console
This message is automatically generated.
> Disable FileCache update for parallel_execution
> -----------------------------------------------
>
> Key: AMBARI-19372
> URL: https://issues.apache.org/jira/browse/AMBARI-19372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 3.0.0
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19372.patch
>
>
> Ambari agent's {{FileCache}} is not thread-safe, hence needs to be disabled
> if {{parallel_execution}} is enabled. The server's
> {{agent.auto.cache.update=false}} setting is not enough to prevent all
> subprocesses from using the file cache, because they are started before the
> setting is received from the server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
