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
It's been demonstrated that BTE will occasionally "hold onto" some cached qEdges beyond their expected expire time. The most likely explanation for this is that BTE is failing to set an expire time, likely by way of being restarted prior to the expire time being set.
There is a likely better way to handle this, but as redis does not store key age, the simplest naive approach is to just add a cron job that eliminates all cached qEdges after some interval (once a day at midnight?).
The text was updated successfully, but these errors were encountered:
tokebe
added
On CI
Related changes are deployed to CI server
On Test
Related changes are deployed to Test server
and removed
On Dev
Related changes are deployed to Dev server
On CI
Related changes are deployed to CI server
labels
Dec 18, 2023
It's been demonstrated that BTE will occasionally "hold onto" some cached qEdges beyond their expected expire time. The most likely explanation for this is that BTE is failing to set an expire time, likely by way of being restarted prior to the expire time being set.
There is a likely better way to handle this, but as redis does not store key age, the simplest naive approach is to just add a cron job that eliminates all cached qEdges after some interval (once a day at midnight?).
The text was updated successfully, but these errors were encountered: