29

I was trying to do a search for new questions using the advanced search tags such as is:question and intags:mine. This normally works well, but today it is not showing any questions newer than 2nd June. For example, try this link which should show all questions in my tags, ordered by newest first:

http://stackoverflow.com/search?tab=newest&q=intags%3amine

Has some back-end script stopped running perhaps?

Edit:

Search appears to be out-of-date for all search type (not just advanced search) and across all SE sites.

Edit: after working fine for a while, the bug is back in July 30th 2014:

  • It got nothing to do with advanced search, all search results are limited to June 2 or before. – Shadow The Dragon Wizard Jun 8 '14 at 12:25
  • 1
    @ShadowWizard Why are search results limited? And what is advanced search then? – DavidG Jun 8 '14 at 12:27
  • Search is not running over the live database itself, whatever code/job that is responsible to index the live database has stopped working and the dev team should bring it back to life. It might take hours, or it might take weeks, really can't tell. Advanced search is not relevant to this bug report, because it affects the whole search mechanism that's why I removed the tag. – Shadow The Dragon Wizard Jun 8 '14 at 12:29
  • 2
    Worth to mention this is cross network: all sites in Stack Exchange appear to be affected. Amazing how nobody noticed until now! – Shadow The Dragon Wizard Jun 8 '14 at 12:32
  • @ShadowWizard Ah I see, should I edit the question or just leave it? – DavidG Jun 8 '14 at 12:32
  • 4
    Might have something to do with the move of servers to the new DC? – rene Jun 8 '14 at 12:36
  • 1
    You can edit and state it's out of date for all kinds of search, in all sites, yes. :) – Shadow The Dragon Wizard Jun 8 '14 at 12:36
  • 1
    @rene good call! When did they move? – Shadow The Dragon Wizard Jun 8 '14 at 12:36
  • 1
    @rene: absolutely. The new elacticsearch cluster lost a chunk of new data, by the looks of it. I noticed it on mobile and assumed it was still indexing. – Martijn Pieters Jun 8 '14 at 14:23
  • 1
    @MartijnPieters Would it take so long to catch up? I assume the search cluster started with a backup of the already indexed data? Or is that not how it works? My bet is on a job that is not running... – rene Jun 8 '14 at 15:00
  • 3
    @rene: Yeah, something is b0rken and stuck. IIRC 2nd of June is the date the site was switched to the Oregon center, so this is an old dataset. – Martijn Pieters Jun 8 '14 at 15:06
  • 1
    No idea what all happened here, but this appears to be resolved now. – Adam Lear Jun 18 '14 at 21:19
  • 1
    @Anna it's back in full glory. – Shadow The Dragon Wizard Jul 30 '14 at 9:10
  • @ShadowWizard Should the status-completed tag be removed from this? And what should I do with my new question? – DavidG Jul 30 '14 at 9:15
  • 1
    Reporting bugs again is better than editing/flagging old ones, @ShadowWizard. The latter is much harder for us to track. I'm on it this time, but for future reference... – Adam Lear Jul 30 '14 at 21:18
5

There was a problem with search indexing that caused this issue.

A recycle of the elastic search nodes sorted it out.

Thanks for reporting!

  • Thanks, if this happens again, what is the ideal course of action? Comment here or post whole new report which will be exact dupe? – Shadow The Dragon Wizard Jul 31 '14 at 9:24
  • 1
    @ShadowWizard - these are all separate occurrences, so I'd rather see a new report than a reopening of an existing one. – Oded Jul 31 '14 at 9:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .