Closed pgwillia closed 5 months ago
@murny says, "Looks like at ~1:41 PM yesterday something happen where a bunch of things couldn’t be found in the database 🤔. So these Solr errors are when we try to look up an object in ActiveRecord and it’s not found (we assume Solr is stale, so we remove the record from Solr). But this also happen in Sidekiq, where we saw a big uptick of ActiveRecord Not Found errors in DOICreateJob’s. It hasn’t happen again since 1PM yesterday (2024-06-11) and no more new errors for this. Don’t understand how this error could happen in a blimp like this though, unless we swung to a different DB for a few seconds or something 🤷 (cause if DB went down or went offline, you would get a different error (timeout or connection error, not record not found) These objects do exist though and I can view them no problem in the search results and show page in production as of right now"
Seems to be a one off and nothing is missing. We'll watch for this to re-occur.
@nmacgreg I wonder if this was related to IST resolving the PostgreSQL database backup/firewall the other day.
View details in Rollbar: https://app.rollbar.com/a/ualbertalib/fix/item/jupiter/1918
https://github.com/ualbertalib/jupiter/blob/66ca00d348625678803e91c56c69daf6ac8d6e5c/app/models/jupiter_core/solr_services/deferred_faceted_solr_query.rb#L146-L154