URLFetch is timing out excessively

50 views
Skip to first unread message

nischalshetty

unread,
Oct 26, 2011, 1:54:05 PM10/26/11
to google-a...@googlegroups.com
I've raised a production issue around 4 hours ago but no one has been able to look into it yet :(

Requests to twitter are timing out excessively. Since we have twitter login, users are not even able to login to the application. Can someone please look into this? 

Brandon Wirtz

unread,
Oct 26, 2011, 2:30:34 PM10/26/11
to google-a...@googlegroups.com

Raise the issue with twitter.  They time out because twitter is too slow. Not Google.  This is a common problem with twitter.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Z0J2_qC7AZUJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

nischalshetty

unread,
Oct 26, 2011, 3:10:45 PM10/26/11
to google-a...@googlegroups.com
I agree twitter times out but this is not because of them. I'm talking about hundreds of timeout every minute.

We have things in place to retry timeouts, but I'm talkin about timeouts even after 3 retries with a timeout of 20 second each. 


Vivek Puri

unread,
Oct 26, 2011, 3:20:40 PM10/26/11
to Google App Engine
+1 . Requests to Facebook are also timing out.

Vivek Puri

unread,
Oct 26, 2011, 3:25:28 PM10/26/11
to Google App Engine

Nischal Shetty

unread,
Oct 26, 2011, 3:30:17 PM10/26/11
to google-a...@googlegroups.com
Done. I too have raised a production issue - http://code.google.com/p/googleappengine/issues/detail?id=6188

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.




--
-Nischal
twitter: NischalShetty
facebook: Nischal

    


Vivek Puri

unread,
Oct 26, 2011, 3:31:53 PM10/26/11
to Google App Engine
Thank you.

On Oct 26, 3:30 pm, Nischal Shetty <nischalshett...@gmail.com> wrote:
> Done. I too have raised a production issue -http://code.google.com/p/googleappengine/issues/detail?id=6188
> twitter: NischalShetty <http://twitter.com/nischalshetty>
> facebook: Nischal <http://facebook.com/nischal>
>
> <http://www.justunfollow.com>     <http://www.buffr.com>

Brandon Wirtz

unread,
Oct 26, 2011, 5:33:27 PM10/26/11
to google-a...@googlegroups.com

So you think that Fetches to only Twitter and FB are broken?   Did you try from a non-Goog Environment?  There are Fail Whales all over today.  

 

And if you are running “Hundreds of API calls a minute” you are likely hitting the API IP Limits since Twitter won’t grant a white list for Google IP’s.

 

You should be using a proxy to access twitter through a single IP what is on the Twitter API white List.

--

You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/YJ2bm0bM_l8J.

Nischal Shetty

unread,
Oct 26, 2011, 5:46:54 PM10/26/11
to google-a...@googlegroups.com
It works from a non google environment. We have a service running on AWS which is working smooth. It's not a whitelist problem because these are signed calls which do not account for rate limiting based on IP.

Someone from google has replied saying the problem is not on their end. I have raised an issue on the twitter discussion forum (stupid of me to not have done that simultaneously). 

Vivek Puri

unread,
Oct 26, 2011, 5:56:52 PM10/26/11
to Google App Engine
Nischal,

Send me link to the issue you report on Twitter. Thank you



On Oct 26, 5:46 pm, Nischal Shetty <nischalshett...@gmail.com> wrote:
> It works from a non google environment. We have a service running on AWS
> which is working smooth. It's not a whitelist problem because these are
> signed calls which do not account for rate limiting based on IP.
>
> Someone from google has replied saying the problem is not on their end. I
> have raised an issue on the twitter discussion forum (stupid of me to not
> have done that simultaneously).
>
> On 26 October 2011 18:33, Brandon Wirtz <drak...@digerat.com> wrote:
>
>
>
>
>
>
>
>
>
> > So you think that Fetches to only Twitter and FB are broken?   Did you try
> > from a non-Goog Environment?  There are Fail Whales all over today.   ****
>
> > ** **
>
> > And if you are running “Hundreds of API calls a minute” you are likely
> > hitting the API IP Limits since Twitter won’t grant a white list for Google
> > IP’s.****
>
> > ** **
>
> > You should be using a proxy to access twitter through a single IP what is
> > on the Twitter API white List.****
>
> > ** **
>
> > ** **
>
> > *From:* google-a...@googlegroups.com [mailto:
> > google-a...@googlegroups.com] *On Behalf Of *nischalshetty
> > *Sent:* Wednesday, October 26, 2011 12:11 PM
> > *To:* google-a...@googlegroups.com
> > *Subject:* Re: [google-appengine] URLFetch is timing out excessively****
>
> > ** **
>
> > I agree twitter times out but this is not because of them. I'm talking
> > about hundreds of timeout every minute.****
>
> > ** **
>
> > We have things in place to retry timeouts, but I'm talkin about timeouts
> > even after 3 retries with a timeout of 20 second each. ****
>
> > ** **
>
> > ** **
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To view this discussion on the web visit
> >https://groups.google.com/d/msg/google-appengine/-/YJ2bm0bM_l8J.
> > To post to this group, send email to google-a...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.****
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-a...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> -Nischal

Nischal Shetty

unread,
Oct 26, 2011, 6:06:53 PM10/26/11
to google-a...@googlegroups.com
I saw the issue that you've reported on twitter. I've subscribed to that. The issue that I reported on twitter has not been approved yet (probably because ur issue is already visible) though @episod from twitter commented that they are looking into the connectivity issue.
facebook: Nischal

    


Jeff Schnitzer

unread,
Oct 26, 2011, 6:14:34 PM10/26/11
to google-a...@googlegroups.com
You mean, the only site on the internet less reliable than twitter?

Jeff
(sorry - I don't have anything constructive to add, but I couldn't help myself)

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

Brandon Wirtz

unread,
Oct 26, 2011, 7:01:01 PM10/26/11
to google-a...@googlegroups.com

Signed calls are still subject to a variable rate limit based on Twitters given load. They throttle up and down based on available capacity.

Description: Image removed by sender.    Description: Image removed by sender.

 

 

image001.jpg
image002.jpg

Nischal Shetty

unread,
Oct 26, 2011, 7:07:34 PM10/26/11
to google-a...@googlegroups.com
Yeah, you are right about that. I had faced it a few months ago following which I moved that part to AWS. The other API calls though in excess are below those variable limits.

I got a reply by twitter on their discussion forum that they are looking into the issue. Hoping they find the cause soon.
    


image001.jpg
image002.jpg

Nischal Shetty

unread,
Oct 27, 2011, 10:30:35 AM10/27/11
to google-a...@googlegroups.com
Twitter has fixed the connectivity issues.
image001.jpg
image002.jpg
Reply all
Reply to author
Forward
0 new messages