You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Brock Noland (Created) (JIRA)" <ji...@apache.org> on 2012/03/29 02:09:36 UTC

[jira] [Created] (FLUME-1077) No error messages printed when hadoop removed from classpath

No error messages printed when hadoop removed from classpath
------------------------------------------------------------

                 Key: FLUME-1077
                 URL: https://issues.apache.org/jira/browse/FLUME-1077
             Project: Flume
          Issue Type: Improvement
          Components: Configuration
    Affects Versions: v1.1.0
            Reporter: Brock Noland


With the config below, if you remove hadoop from the classpath and then try and start the flume source agent and flume collector agents, flume is dead quiet. NO errors nothing.

{noformat}

tail1.sources = src1
tail1.channels = ch1
tail1.sinks = sink1 sink2
tail1.sinkgroups = sg1

tail1.sources.src1.type = exec
tail1.sources.src1.command = tail -F /tmp/acess_log
tail1.sources.src1.channels = ch1

tail1.channels.ch1.type = memory
tail1.channels.ch1.capacity = 500

tail1.sinks.sink1.type = avro
tail1.sinks.sink1.hostname = localhost
tail1.sinks.sink1.port = 6000
tail1.sinks.sink1.batch-size = 1
tail1.sinks.sink1.channel = ch1

tail1.sinks.sink2.type = avro
tail1.sinks.sink2.hostname = localhost
tail1.sinks.sink2.port = 6001
tail1.sinks.sink2.batch-size = 1
tail1.sinks.sink2.channel = ch1

tail1.sinkgroups.sg1.sinks = sink1 sink2
tail1.sinkgroups.sg1.processor.type = failover
tail1.sinkgroups.sg1.processor.priority.sink1 = 1
tail1.sinkgroups.sg1.processor.priority.sink2 = 2

######################################################

collector1.sources = src1
collector1.channels = ch1
collector1.sinks = sink1

collector1.sources.src1.type = avro
collector1.sources.src1.bind = localhost
collector1.sources.src1.port = 6000
collector1.sources.src1.channels = ch1

collector1.channels.ch1.type = memory
collector1.channels.ch1.capacity = 500

collector1.sinks.sink1.type = hdfs
collector1.sinks.sink1.hdfs.path = collector1
collector1.sinks.sink1.hdfs.filePrefix = access_log
collector1.sinks.sink1.channel = ch1

######################################################

collector2.sources = src1
collector2.channels = ch1
collector2.sinks = sink1

collector2.sources.src1.type = avro
collector2.sources.src1.bind = localhost
collector2.sources.src1.port = 6001
collector2.sources.src1.channels = ch1

collector2.channels.ch1.type = memory
collector2.channels.ch1.capacity = 500

collector2.sinks.sink1.type = hdfs
collector2.sinks.sink1.hdfs.path = collector2
collector2.sinks.sink1.hdfs.filePrefix = access_log
collector2.sinks.sink1.channel = ch1
{noformat}

--
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

        

[jira] [Resolved] (FLUME-1077) No error messages printed when hadoop removed from classpath

Posted by "Brock Noland (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brock Noland resolved FLUME-1077.
---------------------------------

    Resolution: Duplicate

See FLUME-1093
                
> No error messages printed when hadoop removed from classpath
> ------------------------------------------------------------
>
>                 Key: FLUME-1077
>                 URL: https://issues.apache.org/jira/browse/FLUME-1077
>             Project: Flume
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: v1.1.0
>            Reporter: Brock Noland
>
> With the config below, if you remove hadoop from the classpath and then try and start the flume source agent and flume collector agents, flume is dead quiet. NO errors nothing.
> {noformat}
> tail1.sources = src1
> tail1.channels = ch1
> tail1.sinks = sink1 sink2
> tail1.sinkgroups = sg1
> tail1.sources.src1.type = exec
> tail1.sources.src1.command = tail -F /tmp/acess_log
> tail1.sources.src1.channels = ch1
> tail1.channels.ch1.type = memory
> tail1.channels.ch1.capacity = 500
> tail1.sinks.sink1.type = avro
> tail1.sinks.sink1.hostname = localhost
> tail1.sinks.sink1.port = 6000
> tail1.sinks.sink1.batch-size = 1
> tail1.sinks.sink1.channel = ch1
> tail1.sinks.sink2.type = avro
> tail1.sinks.sink2.hostname = localhost
> tail1.sinks.sink2.port = 6001
> tail1.sinks.sink2.batch-size = 1
> tail1.sinks.sink2.channel = ch1
> tail1.sinkgroups.sg1.sinks = sink1 sink2
> tail1.sinkgroups.sg1.processor.type = failover
> tail1.sinkgroups.sg1.processor.priority.sink1 = 1
> tail1.sinkgroups.sg1.processor.priority.sink2 = 2
> ######################################################
> collector1.sources = src1
> collector1.channels = ch1
> collector1.sinks = sink1
> collector1.sources.src1.type = avro
> collector1.sources.src1.bind = localhost
> collector1.sources.src1.port = 6000
> collector1.sources.src1.channels = ch1
> collector1.channels.ch1.type = memory
> collector1.channels.ch1.capacity = 500
> collector1.sinks.sink1.type = hdfs
> collector1.sinks.sink1.hdfs.path = collector1
> collector1.sinks.sink1.hdfs.filePrefix = access_log
> collector1.sinks.sink1.channel = ch1
> ######################################################
> collector2.sources = src1
> collector2.channels = ch1
> collector2.sinks = sink1
> collector2.sources.src1.type = avro
> collector2.sources.src1.bind = localhost
> collector2.sources.src1.port = 6001
> collector2.sources.src1.channels = ch1
> collector2.channels.ch1.type = memory
> collector2.channels.ch1.capacity = 500
> collector2.sinks.sink1.type = hdfs
> collector2.sinks.sink1.hdfs.path = collector2
> collector2.sinks.sink1.hdfs.filePrefix = access_log
> collector2.sinks.sink1.channel = ch1
> {noformat}

--
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