[
https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817036#comment-15817036
]
Hudson commented on AMBARI-19444:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #683 (See
[https://builds.apache.org/job/Ambari-branch-2.5/683/])
AMBARI-19444 Log Feeder should be restarted after configuration change
(mgergely:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a96880fb91e8ef67450b9055389e29e1cc5998fc])
* (edit)
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml
* (edit)
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/input.config-ambari.json.j2
> 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
>
> Attachments: AMBARI-19444.patch
>
>
> 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)
