We have a user database lookup capacity issue that is most acute on Site Streams. This is compounded by a bug that causes Hosebird to cache a timed-out database lookup as a negative authentication entry, and then your account can't log in on that one server for the cache duration. Generally if you try again, you'll hit another server and everything will be fine. This strikes randomly, but, very rarely.
Earlier this week we spent a lot of time adding about ten times the database capacity and also fixing this awful bug, but there were a few minor problems along the way, leading to several redeploys and restarts that you may have experienced. Eventually, we ran out of time for the deploy. We'll just mumble through the next week as things are and avoid restarts on our end. If we don't restart, and your client doesn't do a full restart, you should have good Site Streams connectivity through the holidays, and we'll get this out in the New Year. There are a number of minor goodies queued behind this deploy. We'll get there. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Fri, Dec 17, 2010 at 10:54 AM, David <dtran...@gmail.com> wrote: > I have been getting sporadic 401s interleaved with 200s while connected to > Site Streams. I'll either open up a connection and it'll return 401s for a > while, then eventually start returning normal responses, or vice versa. This > issue started cropping up yesterday after the Site Stream restarts. Other > users in the IRC channel seem to be reporting 401s across other endpoints > somewhat sporadically as well. Is this a known issue? Any help would be > greatly appreciated! > > Best, > David > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
