Was having issues queueing up Elasticsearch index jobs...realized I hadn't provisioned Redis for the Heroku app 🤦♂️
Similar Remarks
Still having memory errors with Elasticsearch server. Might just abandon the Heroku add-ons and use AWS. What a headache. I'd prefer not abandoning Elasticsearch since I can run it locally, but if these intermittent errors can't be resolved it might be best to use something like Algolia.
Yep. Done deal. Switching to AWS Elasticsearch, and if that doesn't fix these errors, off to Algolia we go.
I keep breaking the site! Definitely need some automated tests lol. Also having constant errors from Elasticsearch running out of memory. Might switch to a different search provider.
I think searches were breaking due to Searchkick errors caused by memory issues. I think cleaning old indices solved it. Running that nightly now. We'll see if the error crops up again...
Fixed issue with index not being updated. Worker wasn't processing jobs from Searchkick. Nice way to end a long day.
Hmm...having issues setting up Elasticsearch in AWS. Going to stick to the Bonsai Elasticsearch addon for now and add a control panel so I can see memory usage.
Oh. AWS Comprehend topic modeling is $1 per job. Maybe I shouldn't do that just yet. lol
Got a basic similar search working with Elasticsearch. Pretty nifty.