12

Using search for new questions returns yesterday's and older posts for many sites. Tested for localized Stack Overflow...

and other sites such as Mathematics, Super User, Ask Ubuntu, etc.

English Stack Overflow works fine. So does Meta.SE

Possibly related to my previous bug report: Something wrong with tag view in the Android app

Seems this happens again. Now for SO and MSE too.

Improve this question
6
  • 4
    This is not just localized sites but "everyone except en-SO". See: Mathematics, Super User, Ask Ubuntu.
    – user315433
    Sep 10, 2017 at 19:31
  • @Michelle feel free to edit this post according new information. Just checked: it works for MSE.
    – αλεχολυτ
    Sep 10, 2017 at 19:34
  • Okay, I suggested an edit expanding it to "many sites" without claiming an exhaustive list. Meta.SE is special in many ways, essentially a development branch, so I'm not surprised it doesn't have the same bug.
    – user315433
    Sep 10, 2017 at 19:39
  • 2
    My bet is on Nick for breaking it: twitter.com/Nick_Craver/status/906133210156892160
    – rene
    Sep 10, 2017 at 19:49
  • 1
    @rene so how long will re-reindexing take? Hopefully less than 6-8 weeks...
    – Shadow The Spring Wizard
    Sep 11, 2017 at 6:54
  • I'm having this problem on English StackOverflow in the Android app. Questions after Sept 15 or so are not loading. The website works fine, though.
    – Remy Lebeau
    Sep 17, 2017 at 8:34

1 Answer 1

Reset to default
3

Well, as much as I'd like to blame Nick, it's not just his fault. In preparation for our upgrade to Elastic v2.4.6 (on our way to v5.5.2) we started re-indexing all sites in the network on Friday and I kicked off Stack Overflow on Saturday morning. Stack Overflow is a pretty large site to index (46m documents) and it takes about 3 hours at full speed. Indexing that many documents while serving live search traffic hurts the cluster so we decided to introduce an abort function in case we needed to stop it in a hurry.

But... that new functionality had a bug and the deltas that run to keep the indexes in sync with their sites didn't run. I've now fixed the bug and pushed to production. Indexes are catching up now so all should be well in the next hour or two.

Thanks for the heads up!

Improve this answer
1
  • 3
    But some fault is still Nick's, right?
    – Braiam
    Sep 11, 2017 at 11:49

You must log in to answer this question.

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