Recent Action
Meta Discourse has a warning that the whos online plugin is "experimental" and does not work well on large forums. We are not large relatively speaking; but this seems like the logical best place to start to search for the root cause of our recent 502 HTTP errors, since I noticed the DB hangs during that error.
Background
Recently, we have seen issues with the Discourse PostgreSQL DB "hanging" which causes a HTTP 502 error and so as a part of our root cause analysis, I have disabled this plugin for the time being.
The Meta Discourse support site does not run this plugin either, so that might be a clue as well.
After disabling this plugin today, the site seems faster, but that might be an illusion.
The Discourse Whos Online plugin is also not an official Discourse plugin (maybe it is "officially supported" now, not sure?), so it is "technically" not supported (please correct me if this is wrong); so for now, it's disabled... let's see how it goes and hope the 502 errors disappear.
It's kinda' a shame, because many people, including me, like that plugin; but maybe it turns out it is not the problem 
Frankly, I thought for a few seconds about a simple crontab that restarts the data container every so many hours; but I really prefer to find out what is causing the DB "hanging" problem versus just burying the problem with restart and never getting to the root cause.
Thank you for understanding and your patience.
See Also:
