ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19444) Log Feeder should be restarted after configuration change
Date Wed, 11 Jan 2017 05:44:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817269#comment-15817269
] 

Hudson commented on AMBARI-19444:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6403 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6403/])
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=7f09e4c6a7751004132e41d1ccd9ec7e48998231])
* (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/input.config-ambari.json.j2
* (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml


> 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)

Mime
View raw message