ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8303) Write another copy of the config files.
Date Fri, 25 Sep 2015 22:14:05 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako updated AMBARI-8303:
--------------------------------
    Fix Version/s:     (was: 2.1.2)

> Write another copy of the config files.
> ---------------------------------------
>
>                 Key: AMBARI-8303
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8303
>             Project: Ambari
>          Issue Type: Technical task
>          Components: ambari-agent
>    Affects Versions: 2.0.0
>            Reporter: Mingjiang Shi
>
> Enhance the current File API to allow write another copy of the configuration file to
a specified folder.
> ========
> Most config files are created using the File API. Therefore, if enhancing the File API
to allow write another copy of the configuration file, then change could be smaller.
> For any component, if it has configuration files to be monitored, just created the following
2 variables in the params.py:
> 1. monitored_config_files_dir: specify where to duplicate the config files
> 2. monitored_config_files: a list of files to be monitored.
> e.g.
> monitored_config_files = ['/etc/zookeeper/conf/log4j.properties']
> monitored_config_files_dir = '/var/run/ambari-agent/zookeeper'
> Whenever the file in the monitored_config_files list is updated by the File API, a copy
should be saved to the monitored_config_files_dir.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message