[
https://issues.apache.org/jira/browse/AMBARI-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15788581#comment-15788581
]
Miklos Gergely commented on AMBARI-19209:
-----------------------------------------
committed to trunk:
{code:java}
commit 3ba3b8ed374b7b777bd36bf490c5aaef5f43de81
Author: Miklos Gergely <mgerg...@hortonworks.com>
Date: Sat Dec 31 00:58:15 2016 +0100
AMBARI-19209 Separate general Log Search env properties from Log Search
Portal properties
Change-Id: Ib132671dff032379645d6e462ccf848900550c3a
{code}
committed to branch-2.5:
{code:java}
commit 5c3d7dbcf32aabbb0aa7ab308635ee0a38b758c8
Author: Miklos Gergely <mgerg...@hortonworks.com>
Date: Sat Dec 31 00:57:02 2016 +0100
AMBARI-19209 Separate general Log Search env properties from Log Search
Portal properties
Change-Id: Id9b779d7aab3a43ca876dd39f3eb316e5ff432a9
{code}
> Separate general Log Search env properties from Log Search Portal properties
> ----------------------------------------------------------------------------
>
> Key: AMBARI-19209
> URL: https://issues.apache.org/jira/browse/AMBARI-19209
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch
> Affects Versions: 2.5.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19209.patch
>
>
> Some properties in logsearch-env are affecting both the portal and the
> feeders, while others affect only the portal. The latter should be separated
> into a logsearch-portal-env, so logfeeders will be restarted only if those
> properties are changed which affect the whole service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
