3 ms·
Doesnt surprise me to be honest. I've seen this in the past where a backend google search appliance search was triggered for 404 with the query being parts of
by ce4 7y ago
Doesnt surprise me to be honest.
I've seen this in the past where a backend google search appliance search was triggered for 404 with the query being parts of the 404 url.
That overwhelmed the search appliance and led to thread exhaustion on the component in front (ridiculous search timeout)... in the end the whole site went down.
- gberger 7y agoI've read the second sentence 5 times, but I can't understand it. Could you rephrase it please?
- tedunangst 7y agoFront end hit to /article/page-not-here triggers a search in the back end, /search?q=page+not+here.
- ce4 7y agoSorry for that. That was a classic tomcat + reverse proxy setup with a fixed number of tc threads. All were being starved by waiting for the search appliance backend calls to return (60s timeout).