still iam getting same error
5/05/05 12:14:10 INFO source.DefaultSourceFactory: Creating instance of source Twitter, type flume.mytwittersource.MyTwitterSourceForFlume
15/05/05 12:14:10 INFO sink.DefaultSinkFactory: Creating instance of sink: HDFS, type: hdfs
15/05/05 12:14:11 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform… using builtin-java classes where applicable
15/05/05 12:14:11 INFO hdfs.HDFSEventSink: Hadoop Security enabled: false
15/05/05 12:14:11 INFO node.AbstractConfigurationProvider: Channel MemChannel connected to [Twitter, HDFS]
15/05/05 12:14:11 INFO node.Application: Starting new configuration:{ sourceRunners:{Twitter=EventDrivenSourceRunner: { source:flume.mytwittersource.MyTwitterSourceForFlume{name:Twitter,state:IDLE} }} sinkRunners:{HDFS=SinkRunner: { policy:org.apache.flume.sink.DefaultSinkProcessor@731563a4 counterGroup:{ name:null counters:{} } }} channels:{MemChannel=org.apache.flume.channel.MemoryChannel{name: MemChannel}} }
15/05/05 12:14:11 INFO node.Application: Starting Channel MemChannel
15/05/05 12:14:11 INFO instrumentation.MonitoredCounterGroup: Monitored counter group for type: CHANNEL, name: MemChannel: Successfully registered new MBean.
15/05/05 12:14:11 INFO instrumentation.MonitoredCounterGroup: Component type: CHANNEL, name: MemChannel started
15/05/05 12:14:11 INFO node.Application: Starting Sink HDFS
15/05/05 12:14:11 INFO instrumentation.MonitoredCounterGroup: Monitored counter group for type: SINK, name: HDFS: Successfully registered new MBean.
15/05/05 12:14:11 INFO instrumentation.MonitoredCounterGroup: Component type: SINK, name: HDFS started
15/05/05 12:14:11 INFO node.Application: Starting Source Twitter
429:Returned in API v1.1 when a request cannot be served due to the application’s rate limit having been exhausted for the resource. See Rate Limiting in API v1.1.(https://dev.twitter.com/docs/rate-limiting/1.1)
message - Rate limit exceeded
code - 88
Relevant discussions can be found on the Internet at:
http://www.google.co.jp/search?q=506c3b98 or
http://www.google.co.jp/search?q=136e1d5a
TwitterException{exceptionCode=[506c3b98-136e1d5a], statusCode=429, message=Rate limit exceeded, code=88, retryAfter=-1, rateLimitStatus=RateLimitStatusJSONImpl{remaining=0, limit=180, resetTimeInSeconds=1430809245, secondsUntilReset=902}, version=4.0.1}
at twitter4j.HttpClientImpl.handleRequest(HttpClientImpl.java:164)
at twitter4j.HttpClientBase.request(HttpClientBase.java:53)
at twitter4j.HttpClientBase.get(HttpClientBase.java:71)
at twitter4j.TwitterImpl.get(TwitterImpl.java:1950)
at twitter4j.TwitterImpl.search(TwitterImpl.java:290)
at flume.mytwittersource.MyTwitterSource.fetchTweets(MyTwitterSource.java:63)
at flume.mytwittersource.MyTwitterSourceForFlume.start(MyTwitterSourceForFlume.java:29)
at org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
at org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Failed to search tweets: 429:Returned in API v1.1 when a request cannot be served due to the application’s rate limit having been exhausted for the resource. See Rate Limiting in API v1.1.(https://dev.twitter.com/docs/rate-limiting/1.1)
message - Rate limit exceeded
code - 88
15/05/05 12:15:42 INFO lifecycle.LifecycleSupervisor: Stopping lifecycle supervisor 10
