Re: Error 500 problems.

[Jason Toffaletti]

On Monday, November 19, 2012 3:48:00 PM UTC-8, Rick wrote:

For the past week or so I've been getting regular Error 500 timeout problems.
Retrying the query usually works, but occasionally it still fails after 3 retries.

Is anyone else seeing this problem?

We'll look into it, thanks.

 

Any way to contact Topsy to tell them about it?

You just did.

[Jason Toffaletti]

We're not seeing a higher than normal percentage of 500 errors in our logs. Can you give us an example of the type of request you're doing where you see this issue? It could be specifically related to the parameters you're using.

[Jean Véronis]

I confirm: large number of failures, about 1 out of two.

The service is nearly unusable.

Is Topsy reading this? Can we have some information?

Thanks

2012/11/20 Rick <goog...@inboundwriter.com>

For the past week or so I've been getting regular Error 500 timeout problems.
Retrying the query usually works, but occasionally it still fails after 3 retries.

Is anyone else seeing this problem? Any way to contact Topsy to tell them about it?


Rick

[Jean Véronis]

An example:

http://otter.topsy.com/search.json?window=w&type=tweet&locale=fr&allow_lang=fr&perpage=100&q=rihanna&apikey=....

I just tried again a minute ago and got this:

Error: Request timeout reached

This is the behavior my clients have been getting for about a week.

[Jason Toffaletti]

Thanks so much Rick and Jean. We put some new Otter servers into the rotation about a week ago and it seems likely these new servers are the source of the 500 errors you've both been seeing. I'm going to ask that these servers be removed to see if the situation improves for you.

On Tuesday, November 20, 2012 9:23:55 AM UTC-8, Rick wrote:

winterwell.jtwitter.TwitterException$E50X: Error HTTP/1.1 500 Error Error: Request timeout reached http://otter.topsy.com/searchdate.json?maxtime=1353430873&perpage=100&q=content%2Bstrategy&mintime=1350838873&apikey=.................
winterwell.jtwitter.TwitterException$E50X: Error HTTP/1.1 500 Error Error: Request timeout reached http://otter.topsy.com/searchdate.json?maxtime=1353430873&perpage=100&q=blog%2Bposts&mintime=1350838873&apikey=..................

and a few thousand others.

Rick

[Jean Véronis]

Many thanks for your help, Jason! I'll tell you if things get better, let's say tomorrow (I am not sure how long it will take on your side to do the modification)

2012/11/20 Jason Toffaletti <ja...@topsy.com>

[Jean Véronis]

Same here: back to normal.

Thanks again !

--jv

2012/11/21 Rick <goog...@inboundwriter.com>

Thanks for your help.
Things look like they're back to normal now, we run a job every 1/2 hour that asks for a few hundred queries, and the last 2 have run without failure.

Rick