ravenzachary encountered search issues after upgrading to 2.5.0.beta6, resulting in 502 errors or “Site is under extreme load, search is disabled” messages. Despite trying to regenerate the search index, the issue persisted.
@codinghorror suggested that the recent PostgreSQL 12 upgrade might take time to stabilize. ravenzachary confirmed the PostgreSQL 12 upgrade and followed the instructions to complete it.
After rebuilding the app, ravenzachary reported that search was working again, but it was slow compared to 2.5.0b3. neounix advised checking the integrity of PostgreSQL indexes, providing a link to a guide on how to do so using amcheck.
I just upgraded to 2.5.0.beta6. After the successful upgrade completed, all searches fail resulting in the following message after an extended period of think time (animating circle):
I have tried rebooting the server, and this does not resolve the issue.
Any insight? Thank you.
UPDATE 1: I am currently regenerating the search index. I have no idea if this will help.
UPDATE 2: rake search:reindex did not fix the 502 error issue.
UPDATE 3: Sometimes instead of getting a 502 error, I get the message, “Site is under extreme load, search is disabled, try again later.” This message has never appeared before. This is not a high-use Forums.
Does the latest docker image use PostgreSQL 12 and @codinghorror how do you define “take time”? Should I let it be to resolve itself or do I need to fix something?
