Search 502 errors in 2.5.0.beta6

[ravenzachary]

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.

[codinghorror (Jeff Atwood)]

If the database was upgraded to Postgres 12 it might take time for things to stabilize?

[ravenzachary]

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?

UPDATE: Yes, PostgeSQL 12.

[ravenzachary]

Ok, I went and read this:

PostgreSQL 12 update

WARNING! If your database is very large, you will need a lot of extra disk space (2x database size) and should be very careful with this upgrade! We just landed the long waited PostgreSQL major version upgrade. Any site admins rebuilding Discourse from the command line will be upgraded to PostgreSQL 12 from the old PostgreSQL 10. We are running this new version for a while on Meta, and everything is working fine. PostgreSQL 12 brings lots of improvements that will be automatical…

I received the following message, so I assume the upgrade to PostreSQL 12 worked for me:

Upgrade Complete

To complete the upgrade, rebuild again using:

./launcher rebuild app

I am curious if this search bug will fix itself or if I need to do something.

[ravenzachary]

Ok, search is working again on 2.5.0b6, but it’s really slow compared to 2.5.0b3.

Any advice?

[neounix (Dark Matter)]

Hello @ravenzachary

You might consider checking the integrity of your PostgreSQL indexes and making sure they are working properly and not corrupted.

[ravenzachary]

Thank you. What commands would I use for that?

[neounix (Dark Matter)]

Here ya go @ravenzachary

Use amcheck to Check PostgreSQL Index Integrity (Corruption)

Lately, I have read a number of Discourse topics on meta about “index corruption” in both PostgreSQL 10 and 12. One of the take-a-ways from these discussions is that it may be important or interesting for some sys admins to check the integrity of their Discourse PostgreSQL 10 indexes if they are experiencing performance problems or perhaps before performing an upgrade to PostgreSQL 12. For those who might want to perform this check, I have tested amcheck on two differernt Discourse (PostgreSQ…