You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Alexander Alten-Lorenz (JIRA)" <ji...@apache.org> on 2013/01/14 09:02:12 UTC
[jira] [Commented] (FLUME-1012) Sysinit startup not possible
[ https://issues.apache.org/jira/browse/FLUME-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552488#comment-13552488 ]
Alexander Alten-Lorenz commented on FLUME-1012:
-----------------------------------------------
Fixed and marked as resolved (tested with in Flume-1.2.0).
> Sysinit startup not possible
> ----------------------------
>
> Key: FLUME-1012
> URL: https://issues.apache.org/jira/browse/FLUME-1012
> Project: Flume
> Issue Type: Brainstorming
> Components: Configuration
> Affects Versions: NG alpha 2
> Reporter: Alexander Alten-Lorenz
> Assignee: Alexander Alten-Lorenz
> Labels: features, sysinit, system
> Fix For: v1.2.0, v1.4.0
>
>
> Atm flume isn't ready to start via sysinit, because its need a agent definition at startup:
> bin/flume-ng agent -n NAME -f conf/flume-conf.properties.template
> which reflect the name.foo in the config files. An easy improvement could be to improve the Node name check from missing node name into all node names.
> Tech:
> ====
> bin/flume-ng agent -f conf/flume-conf.properties.template
> java.lang.IllegalStateException: Node name not specified in node.Application (Application.java):
> Code:
> Preconditions.checkState(configurationFile != null,
> "Configuration file not specified");
> Preconditions.checkState(nodeName != null, "Node name not specified");
> Here flume nodeManager could iterate over all name.foo and start all flows. If one or more fails, throw an exception and go to the next available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira