You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Miklos Gergely (JIRA)" <ji...@apache.org> on 2017/01/10 13:08:58 UTC

[jira] [Updated] (AMBARI-19444) Log Feeder should be restarted after configuration change

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

Miklos Gergely updated AMBARI-19444:
------------------------------------
    Description: If any of the <service-name>-logsearch-conf property is modified then the logfeeders should be restarted to work with the updated configs  (was: If any of the <service-name>-logsearch-conf property is modified then the logfeeders should be restarted to work with the updated configs
Options)

> Log Feeder should be restarted after configuration change	
> ----------------------------------------------------------
>
>                 Key: AMBARI-19444
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19444
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 2.5.0
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>             Fix For: 2.5.0
>
>
> If any of the <service-name>-logsearch-conf property is modified then the logfeeders should be restarted to work with the updated configs



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