You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During its periodic, cron-initiated reindex, master pipeline wants to process new records. So, retrieves the timestamp of when it last reindexed (which is stored in its postgres key/value table). As expected, this timestamp is used in a filter to generate a list of new bibcodes. However, the timestamp is also immediately updated. So if we fail to queue the bibcodes and then process them, they will be skipped during the next reindex. This happened when all the servers in SDC crashed on Jan 24 2019.
The text was updated successfully, but these errors were encountered:
During its periodic, cron-initiated reindex, master pipeline wants to process new records. So, retrieves the timestamp of when it last reindexed (which is stored in its postgres key/value table). As expected, this timestamp is used in a filter to generate a list of new bibcodes. However, the timestamp is also immediately updated. So if we fail to queue the bibcodes and then process them, they will be skipped during the next reindex. This happened when all the servers in SDC crashed on Jan 24 2019.
The text was updated successfully, but these errors were encountered: