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 Lorenz-Alten (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/03/03 09:55:57 UTC

[jira] [Issue Comment Edited] (FLUME-1012) Sysinit startup not possible

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

Alexander Lorenz-Alten edited comment on FLUME-1012 at 3/3/12 8:55 AM:
-----------------------------------------------------------------------

Wouldn't work, here a example from a config file:
(# removed)
syslog-agent.sources = Syslog
syslog-agent.channels = memoryChannel-1
syslog-agent.sinks = console

syslog-agent.sources.Syslog.type = syslogTcp
syslog-agent.sources.Syslog.port = 5140

syslog-agent.sources.Syslog.channels = memoryChannel-1
syslog-agent.sinks.console.channel = memoryChannel-1
syslog-agent.sinks.console.type = logger
syslog-agent.channels.memoryChannel-1.type = memory

(# removed)
exec-agent.sources = ExecTail
exec-agent.channels = memoryChannel-2
exec-agent.sinks = console-1

exec-agent.sources.tail.type = exec
exec-agent.sources.tail.command = tail -f /var/log/secure

exec-agent.sources.ExecTail.channels = memoryChannel-2
exec-agent.sinks.console-1.channel = memoryChannel-2
exec-agent.sinks.console-1.type = logger
exec-agent.channels.memoryChannel-2.type = memory

https://issues.apache.org/jira/browse/FLUME-1016 adress the missing -c --config switch
                
      was (Author: alo.alt):
    Wouldn't work, here a example from a config file:
######## syslog agent ############
syslog-agent.sources = Syslog
syslog-agent.channels = memoryChannel-1
syslog-agent.sinks = console

syslog-agent.sources.Syslog.type = syslogTcp
syslog-agent.sources.Syslog.port = 5140

syslog-agent.sources.Syslog.channels = memoryChannel-1
syslog-agent.sinks.console.channel = memoryChannel-1
syslog-agent.sinks.console.type = logger
syslog-agent.channels.memoryChannel-1.type = memory

###### exec agent ##############
exec-agent.sources = ExecTail
exec-agent.channels = memoryChannel-2
exec-agent.sinks = console-1

exec-agent.sources.tail.type = exec
exec-agent.sources.tail.command = tail -f /var/log/secure

exec-agent.sources.ExecTail.channels = memoryChannel-2
exec-agent.sinks.console-1.channel = memoryChannel-2
exec-agent.sinks.console-1.type = logger
exec-agent.channels.memoryChannel-2.type = memory

https://issues.apache.org/jira/browse/FLUME-1016 adress the missing -c --config switch

                  
> 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 Lorenz-Alten
>              Labels: features, sysinit, system
>             Fix For: v1.1.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira