I have a 3-node elastic search cluster which is running fine with twitter
river. I want to three different rivers :-
- the public stream
- a filtered stream based on keywords
- a filtered stream based on selected users
However, whenever I start more than one river, I start receiving multiple
errors related to rate limit :-
Returned by the Streaming API:
Too many login attempts in a short period of time.*
Running too many copies of the same application authenticating with the
same account name.*
Easy there, Turbo. Too many requests recently. Enhance your calm.
[2013-12-11 23:13:33,701][WARN ][river.twitter ] [Hyde]
[twitter][my_twitter_river2] stream failure, restarting stream...
420:Returned by the Search and Trends API when you are being rate limited
I was wondering if its normal behavior (I do know that streaming api can
return something similar if there are too many tweets matching the
criterion) but I am not sure if I should be receiving them so frequently.
Also, is it ok to have multiple rivers using the same oauth, or is it
better to create different users/app for each river.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ea32550c-054d-46a7-bde8-004dfc41bc8a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.