If for some reason a future is unable to be resolved (like session_id miraculously getting wiped from the session table), the global controller keeps polling that future to see if it can clean it up, without clearing up everything else, leading to no requests getting fulfilled afterwards and all requests getting backed up.
Some fixes:
- Set a limit for the future to automatically expire (quick fix, not recommended since we don't know how long a request could reasonably take and it would still shut down the whole system)
- Get the global controller to skip over it and come back later
If for some reason a future is unable to be resolved (like session_id miraculously getting wiped from the session table), the global controller keeps polling that future to see if it can clean it up, without clearing up everything else, leading to no requests getting fulfilled afterwards and all requests getting backed up.
Some fixes: