do not use collector as a node name
-----------------------------------
Key: FLUME-740
URL: https://issues.apache.org/jira/browse/FLUME-740
Project: Flume
Issue Type: Bug
Components: Docs
Affects Versions: v0.9.4
Reporter: Aaron Morton
Priority: Trivial
I'm using the 0.9.4 tar distro and running through the docs, when I got up to
this point
http://archive.cloudera.com/cdh/3/flume/UserGuide/index.html#_tiering_flume_nodes_agents_and_collectors
And tried to use this config (through the web console)
10.0.1.150 : console | agentSink("localhost",35853) ;
collector : collectorSource(35853) | console ;
There was a big bang....
{code:java}
com.cloudera.flume.conf.FlumeSpecException: Parser error: unexpected
'collector' at position 0 line 2: '10.0.1.150 : console |
agentSink("localhost",35853) ;
collector : collectorSource(35853) | console ;'
at com.cloudera.flume.conf.FlumeSpecGen.generate(FlumeSpecGen.java:278)
at
com.cloudera.flume.master.MultiConfigCommand$1.exec(MultiConfigCommand.java:77)
at
com.cloudera.flume.master.CommandManager.exec(CommandManager.java:266)
at
com.cloudera.flume.master.CommandManager.handleCommand(CommandManager.java:205)
at
com.cloudera.flume.master.CommandManager$ExecThread.run(CommandManager.java:236)
{code}
My work around was to change the collector flume node name from "collector" to
"coll" and this then worked as a config
10.0.1.150 : console | agentSink("localhost",35853) ;
coll : collectorSource(35853) | console ;
looks like "collector" is an antlr token
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
