You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2015/04/07 07:10:12 UTC
[jira] [Commented] (FLUME-2655) Monitoring should start before all
other components
[ https://issues.apache.org/jira/browse/FLUME-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482603#comment-14482603 ]
Ashish Paliwal commented on FLUME-2655:
---------------------------------------
IMHO, this is the correct behaviour, unless I am missing something. Agent is considered started only when all the components have started.
Assume if we start the monitoring system before and the monitoring system adds the Agent to processing pool, like, to an ELB for processing.
There is a related JIRA for exposing Agent state, may be that is better way of handling the scenario.
> Monitoring should start before all other components
> ---------------------------------------------------
>
> Key: FLUME-2655
> URL: https://issues.apache.org/jira/browse/FLUME-2655
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
>
> Some monitoring systems look at the web server to figure out if the flume agent has started or not. But if the channel takes a while to start, the tools think the flume agent have not started yet. So we must start the monitoring server before the components are started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)