Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Flume, mail # dev - Avro Sink failure


+
Harish Mandala 2012-10-03, 21:05
Copy link to this message
-
Re: Avro Sink failure
Hari Shreedharan 2012-10-03, 21:22
Harish,

Which branch did you build the code from? Seems like you are missing some Avro generated classes in the class path. This is quite weird, since those classes are in the same jar as the AvroSink. Can you try building using mvn clean install?

Regards,
Hari
--
Hari Shreedharan
On Wednesday, October 3, 2012 at 2:05 PM, Harish Mandala wrote:

> Hello,
>
> Avro Sink does not seem to work. From flume.log :
>
> 03 Oct 2012 20:47:42,575 ERROR [lifecycleSupervisor-1-5]
> (org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run:238) -
> Unable to start SinkRunner: {
> policy:org.apache.flume.sink.DefaultSinkProcessor@7eda18ac counterGroup:{
> name:null counters:{} } } - Exception follows.
> java.lang.Error: Unresolved compilation problems:
> The import org.apache.flume.source cannot be resolved
> The import org.apache.flume.source cannot be resolved
> The import org.apache.flume.source cannot be resolved
> AvroSourceProtocol cannot be resolved to a type
> Callback cannot be resolved to a type
> The method getClient(Class<Callback>, Transceiver) from the type
> SpecificRequestor refers to the missing type Callback
> AvroSourceProtocol cannot be resolved to a type
> Status cannot be resolved to a type
> Status cannot be resolved to a type
> AvroFlumeEvent cannot be resolved to a type
> AvroFlumeEvent cannot be resolved to a type
> Callback cannot be resolved to a type
> AvroFlumeEvent cannot be resolved to a type
> AvroFlumeEvent cannot be resolved to a type
> AvroFlumeEvent cannot be resolved to a type
> AvroFlumeEvent cannot be resolved to a type
> Status cannot be resolved to a type
> Status cannot be resolved to a type
> Callback cannot be resolved to a type
> Status cannot be resolved to a type
> Status cannot be resolved to a type
> Status cannot be resolved to a variable
>
> at
> org.apache.flume.api.NettyAvroRpcClient.<init>(NettyAvroRpcClient.java:51)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> at java.lang.Class.newInstance0(Class.java:372)
> at java.lang.Class.newInstance(Class.java:325)
> at
> org.apache.flume.api.RpcClientFactory.getInstance(RpcClientFactory.java:80)
> at org.apache.flume.sink.AvroSink.createConnection(AvroSink.java:182)
> at org.apache.flume.sink.AvroSink.start(AvroSink.java:242)
> at
> org.apache.flume.sink.DefaultSinkProcessor.start(DefaultSinkProcessor.java:46)
> at org.apache.flume.SinkRunner.start(SinkRunner.java:79)
> at
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:236)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
>
> /////////////////
>
> The relevant section from flume.conf:
>
> agent1.sinks.avro-sink1.channel = ch_httpsource_avrosink
> agent1.sinks.avro-sink1.type = avro
> agent1.sinks.avro-sink1.bind = 127.0.0.1
> agent1.sinks.avro-sink1.hostname = 127.0.0.1
> agent1.sinks.avro-sink1.port = 41414
>
> /////////////////
>
> Also, the tests conducted for "mvn package" fail.
>
> What could the problem be?
>
> Regards,
> Harish
>
>
+
Harish Mandala 2012-10-05, 14:01