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
A request to a dead http endpoint will either time out, or reject immediately
A dead discord (channel removed, permissions issues) will return an error by the discord API
In the case of timeout, connection will be open until timeout, so it's holding a TCP connection open for 30s (or whatever the timeout is set to) open, for nothing.
We should have a strategy to disable dead subscribers.
Add a status column in the subscribers/subscriptions table
Everyone has status ALIVE by default
Add a last_alive column in the subscribers/subscriptions table
Touch that column on success request
Each time we send a request, and it fails, we check that column and see for how long it was dead.
If dead for more than X days, we mark the subscriber as dead (update status to DEAD)
We send webhook events only to alive subscribers
This strategy will avoid wasting resources on dead subscribers.
The text was updated successfully, but these errors were encountered:
Subscribers (http and discord) can both die.
In the case of timeout, connection will be open until timeout, so it's holding a TCP connection open for 30s (or whatever the timeout is set to) open, for nothing.
We should have a strategy to disable dead subscribers.
status
column in the subscribers/subscriptions tableALIVE
by defaultlast_alive
column in the subscribers/subscriptions tableDEAD
)This strategy will avoid wasting resources on dead subscribers.
The text was updated successfully, but these errors were encountered: