[
https://issues.apache.org/jira/browse/FLUME-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291368#comment-13291368
]
E. Sammer commented on FLUME-1261:
----------------------------------
The reason this isn't a hard error is because Flume was designed to support hot
reconfiguration (ideally at least - it doesn't today). This means that you may
want to start the daemon with an agent name that's not yet defined. There's a
larger discussion about whether we really need to support reconfiguration
(without a daemon restart), but, as defined, it's not a bug, per se.
> Flume doesn't throw a warning or an error if you pass an undefined agent
> ------------------------------------------------------------------------
>
> Key: FLUME-1261
> URL: https://issues.apache.org/jira/browse/FLUME-1261
> Project: Flume
> Issue Type: Bug
> Reporter: Rosepriya
> Priority: Minor
>
> bin/flume-ng agent --conf ./conf/ -f conf/flume.conf -n agentfoo
> If I try to pass an undefined agent (e.g. agentfoo) by mistake, while
> starting flume doesn't warn or throw any error. There should be some
> indication regarding this misconfiguration in the logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
