This usually happens during peak tweet times and the search servers
get out of sync updating the indexes across all of the boxes. So, when
you refresh, you might be getting results from a different server with
a non-identical set of results. We're working to eliminate these
discrepancies, but as you can imagine it's a tricky problem.

On Fri, Sep 11, 2009 at 2:20 PM, Voolkan <> wrote:
> Something really weird seems to be going on with the search today.
> I first noticed I couldn't search for my own Tweets; a query for
> "voolkan #jobs ny" for instance used to turn up my latest tweets about
> jobs in New York, now it won't return any results posted since
> yesterday.
> When trying to investigate this, I just did some more general
> searches--just the #jobs hash, for instance--and noticed some strange
> things going on. First, every result coming back was posted three
> minutes ago or longer--#jobs is a very active hash, so that's
> obviously not the case.
> Later, more recent results were coming back, but seemed to be mixed in
> all together. Searching repeatedly would show the same tweets shifting
> up and down, before and after other tweets that had supposedly been
> posted at different times.
> Finally, updating search results doesn't really updating anything. I'm
> informed that there are "98 new posts since my search," click the
> refresh button, and have a small handful pop up.
> Does anyone know what's going on here?

Reply via email to