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
Describe the bug
Subscription accountability has a condition where, when running at large scale, values can become out of date. This bug exists since cue3 and a hotfix has been in place at imageworks since it was first uncovered. The root cause for this issue has never been fixed.
The hotfix was integrated into the open source repo at #1380 as a database function, but this function needs to be called on a schedule, something that's not possible (AFAIK) on postgres. SPI's current setup uses a cronjob on the db server to trigger the function every 2 hours, but this setup is far from ideal.
Expected behavior
Ideally this function should be called on a schedule by cuebot and not require an external cronjob. Something to take into consideration is that cuebot might have multiple instances active.
The text was updated successfully, but these errors were encountered:
Describe the bug
Subscription accountability has a condition where, when running at large scale, values can become out of date. This bug exists since cue3 and a hotfix has been in place at imageworks since it was first uncovered. The root cause for this issue has never been fixed.
The hotfix was integrated into the open source repo at #1380 as a database function, but this function needs to be called on a schedule, something that's not possible (AFAIK) on postgres. SPI's current setup uses a cronjob on the db server to trigger the function every 2 hours, but this setup is far from ideal.
Expected behavior
Ideally this function should be called on a schedule by cuebot and not require an external cronjob. Something to take into consideration is that cuebot might have multiple instances active.
The text was updated successfully, but these errors were encountered: