Thanks for the update Dewald. Keep us posted if things change.
On Tue, Aug 11, 2009 at 6:26 AM, Dewald Pretorius<dpr...@gmail.com> wrote:
> I am now doing geometric backoffs on 502s and connection refuses.
> I did not do exact math, but I seem to be getting between 2 and 5
> connection refuses and 502s (combined) per second, and 95%+ of those
> requests get a 200 OK at the first retry.
> I think it's really good performance given the strain that your system
> is under.
> On Aug 10, 3:40 pm, Ryan Sarver <rsar...@twitter.com> wrote:
>> Thanks Dewald. Generally speaking if you see a 502/503 you should do a
>> geometric back off instead of just immediately re-requesting.
>> Is anyone else seeing the X-RateLimit header not showing up some times?
>> Thanks, Ryan
>> On Mon, Aug 10, 2009 at 8:35 AM, Dewald Pretorius <dpr...@gmail.com> wrote:
>> > Ryan,
>> > The 502s don't really bother me. It just slows me down a bit. My
>> > Twitter lib automatically retries a request that 502'd.
>> > The 200 OK responses that come back with the X-RateLimit headers
>> > missing happen on all kinds of requests, both GETs and POSTs (more on
>> > GETs as far as I can tell), and as far as I can see there is no
>> > pattern. One request would return headers, and the very next request
>> > to the same API method would not return the headers. Are these perhaps
>> > requests have have been 302'd? I can't really check because cURL is
>> > following the redirects on GETs.
>> > Dewald
>> > On Aug 10, 12:19 pm, Ryan Sarver <rsar...@twitter.com> wrote:
>> > > Can you all provide full packet dumps of the issues you are seeing? That
>> > > will help us debug the type of request you are making and what the full
>> > > response looks like.
>> > > Thanks, Ryan
>> > > On Mon, Aug 10, 2009 at 8:15 AM, Duane Roelands <
>> > duane.roela...@gmail.com>wrote:
>> > > > My users are seeing these as well.
>> > > > On Aug 10, 10:22 am, Dewald Pretorius <dpr...@gmail.com> wrote:
>> > > > > Just to let you guys know that 502 Bad Gateway responses are coming
>> > > > > thick and fast this morning (Monday).
>> > > > > Dewald