I experienced the problem for the last time today - in fact now
yesterday - at 15:55 and after 5 minutes Phirehose reconnected.

[22-Feb-2010 15:55:25] Phirehose: Consume rate: 0 status/sec (1
total), avg enqueueStatus(): 0.05ms, avg checkFilterPredicates():
0.01ms (3 total) over 60 seconds.
[22-Feb-2010 16:01:22] Phirehose: Idle timeout: No statuses received
for > 300 seconds.  Reconnecting.


On Feb 22, 7:51 pm, John Kalucki <j...@twitter.com> wrote:
> A number of developers have reported abandoned connection issues on the
> Streaming API starting, perhaps, about two weeks ago. The symptoms include a
> long-established TCP connection to stream.twitter.com going quiet, with the
> connection mysteriously held open for perhaps hours afterward. After sorting
> through a lot of conflicting data and chasing a few wild geese, I finally
> reproduced this problem at Feb 22 15:55 UTC (7:55am PST). I'd imagine that a
> number of streams were abandoned at this time. If you had a correlative
> experience within a minute or so of 15:55 UTC, please respond to this
> message.
> We currently suspect an infrequent hardware load balancer issue, perhaps
> related to a recent configuration change. The appearance is that the load
> balancer is, for whatever reason, dropping valid connections, closing the
> connection to the Streaming API servers, but not sending a TCP FIN or TCP
> RST to the client. This is bad. We're treating this as a critical production
> issue and working through the details with network operations. I'll follow
> up as we learn more.
> -John Kaluckihttp://twitter.com/jkalucki
> Infrastructure, Twitter Inc.

Reply via email to