Hopefully I've put the Search crashing to bed for a while at least.
Our search feature is backed by an Elasticsearch cluster on the Virtual Server I pay for that hosts PB and several other Churches and other websites.
The Elasticsearch cluster would simply stop recently and then searh would trown off errors because there was no Elasticsearch service to serve the queries. I'm broadly knowldegeable in the ditital ecosystem and know how Elasticsearch operates but I'm not a Linux expert or an ELK stack expert so I couldn't figure out what was going on. I even set up a CRON job to stop the service every day and turn it back on hoping it would solve the problem.
Today I called the host and they told me I was close to my memory limit and I think that's the reason. I was able to change the plan that doubled the amount of memory for the server and that ought to take care of the issue.
Our search feature is backed by an Elasticsearch cluster on the Virtual Server I pay for that hosts PB and several other Churches and other websites.
The Elasticsearch cluster would simply stop recently and then searh would trown off errors because there was no Elasticsearch service to serve the queries. I'm broadly knowldegeable in the ditital ecosystem and know how Elasticsearch operates but I'm not a Linux expert or an ELK stack expert so I couldn't figure out what was going on. I even set up a CRON job to stop the service every day and turn it back on hoping it would solve the problem.
Today I called the host and they told me I was close to my memory limit and I think that's the reason. I was able to change the plan that doubled the amount of memory for the server and that ought to take care of the issue.
