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...
Similar Remarks
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.
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.
Was having issues queueing up Elasticsearch index jobs...realized I hadn't provisioned Redis for the Heroku app 🤦♂️
Friday! Time to tidy up the remark details/similar remarks page. Really rough layout. Also seeing some weirdness with similar remarks. Might need to tweak how those searches run.
Fixed issue with index not being updated. Worker wasn't processing jobs from Searchkick. Nice way to end a long day.
Had tons of fun at the Leupold Fall Classic in Navasota. They struck two stages due to ranging error and visibility issues, so I got 57 of 73. Struggled a little bit on this PRS barricade stage, and ruptured my bag 🙁 Still a great result. 25th out of 89 shooters.
Stable search for the past few days, as far as I can tell. Hmm. I do need to resolve some issues with some image-only remarks not having any similar remark results. Sounds like a nice weekend project.
Alright, added internal tags for NLP data extracted with AWS Comprehend as well as conversions for searches. Still need to actually use that data in searches, though.
Couldn't sleep. Been a while since I stayed up through the night. Hopefully it doesn't affect my recovery. Tomorrow's bike workout is a tough one.