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.
Similar Remarks
Hmmm, codes 21, 25, and 26 from the cruiser. O2 sensor, apparently. I'll have to figure that out another weekend though. Need to load another 200 rounds for two matches next weekend.
Was having issues queueing up Elasticsearch index jobs...realized I hadn't provisioned Redis for the Heroku app 🤦♂️
Yep. Done deal. Switching to AWS Elasticsearch, and if that doesn't fix these errors, off to Algolia we go.
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.
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.
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.
Had a rough time at yesterday's PRS match. Stability issues, plus the fatigue from standing around in the heat...going to get a chair and tactical wagon for next time. Chris at 5H gave me some pointers on shooting from a big. Super helpful, can't wait to try again.
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.
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...