3 ms·
Would be definitely interesting to read a report on what triggers this error! I don’t think it is a tile error as presumably the backend that collects all the a
by theK 4y ago
Would be definitely interesting to read a report on what triggers this error! I don’t think it is a tile error as presumably the backend that collects all the answers would be set up in a way that is resilient to upstream errors. So maybe the core results compiler?
- faizshah 4y agoI'm not sure exactly how it works but if you look at the network requests for "how many emojis ios" vs "how many emojis android" the html for the initial page contains an internal server error whereas the android version contains some more javascript which contains the search results.
- 1f60c 4y agoI don't think the public will ever learn what went wrong here, but whichever Googler fixes this will have one heck of a war story to tell over drinks.
- shadowgovt 4y agoThe likeliest candidate is probably the final render step. Under the hood, search farms the query out to multiple backends, gathers partials from them, and then composites those partials into the final rendered page. For an actual 500 to surface to the user, that final compositing step is probably what fails; gathering and compositing are already robust against an individual backend failing to return a result. I'm on board with other people's suggestions that asking a question like this is tripping over a site that surfaced an emoji in their site title that is choking the Unicode library that Google is relying upon.