You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sean Roberts (JIRA)" <ji...@apache.org> on 2019/01/21 19:17:00 UTC
[jira] [Commented] (AMBARI-25104) Default for
agent.auto.cache.update changed to false in ambari-agent
[ https://issues.apache.org/jira/browse/AMBARI-25104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748167#comment-16748167 ]
Sean Roberts commented on AMBARI-25104:
---------------------------------------
After reviewing we don't think it is defaulting to agent.auto.cache.update=false.
Instead there is something causing /var/lib/ambari-agent/cache/host_scripts not to be updated.
We've confirmed across several Ambari 2.7.3 installations that host_scripts is never updated, and according to the ambari-agent.log at DEBUG level, the path is never even attempted to be updated.
> Default for agent.auto.cache.update changed to false in ambari-agent
> --------------------------------------------------------------------
>
> Key: AMBARI-25104
> URL: https://issues.apache.org/jira/browse/AMBARI-25104
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.7.3
> Reporter: Attila Csaba Marosi
> Priority: Major
>
> The default for *agent.auto.cache.update* has changed to *false*, as e.g., contents/changes of hosts_scripts/ directory are not pushed to agents by default.
> If we add an explicit *agent.auto.cache.update=true* to ambari-agent.ini then we get the behavior as was in Ambari 2.6.2.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)