This shouldn't be happening. There's most likely a problem with your client implementation, or you are connecting with the same account twice. Email me with your account, details on how your client is implemented, and the time in UTC that this has happened (use date -u), and I'll see what I can tell from the logs.
-John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Oct 26, 8:08 am, Narayan <lakshminaarayana...@gmail.com> wrote: > Hi, > > We have encountered this issue often in the past - I wanted to see if > you have a solution for this or are aware of this already. > > We use the follow, bird-dog method of the Streaming API and sometimes, > the data just stops flowing. The pipe doesn't disconnect though - it > just kind of hangs. I currently have some timeouts configured based on > the incoming data speed to counter this. However, it means I have to > restart the servers every time incoming data speed is zero for an > extended period of time (around 5-10 minutes). And yes, I'm sure there > is valid data available in that time period - it just doesn't come in > the existing pipe we have. > > Are you aware of this issue? If so, is there anything we can do to > avoid this from happening? > > Thanks, > Lakshmi Naarayanan R
