4 ms·
After yesterday's outage they admitted that their elasticsearch index for issues/prs lost data. They seem to have changed the primary source of data in the iss
by stabbles 6mo ago
After yesterday's outage they admitted that their elasticsearch index for issues/prs lost data.
They seem to have changed the primary source of data in the issues and pull requests tabs (w/o filters applied) from the underlying database to the elasticsearch search index, which has the side effect that there's a noticeable delay between state change of an issue/pr and an update in the UI. But as seen today, these can get out of sync, and apparently they even had data loss in the index.
I would really like to know their reasoning for making that change. I can totally imagine that they wanted to "simplify" so the UI uses only a single data source instead of two.
As a user it's incredibly annoying to have a delay between issue/pr state changes and the search index picking it up.
- jrochkind1 6mo agoYeah, I have been noticing weird things with Issues and PRs, including outdated state, for months now. When the outage happened yesterday I sort of figured it was something I had been noticing building up or something.