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 hard to diagnose but I've anecdotally noticed that during peak times (the latest user influx) there are posts that don't end up in the Blacksky feed that should (people using #AddToBlacksky, existing members, etc)
The firehose isn't getting "too-slow" errors. Issue seems to happen locally as well.
Step 1 of this would be to have a reliable way to know if messages have been missed (optimistically consuming 100% of the firehose at all times until filtering arrives).
Step 2 would be having a way to go back and get those missed messages.
Without either of these I have no way to know if folks were trying to get on Blacksky and end up having to add them manually.
Note: Firehose is generic and doesn't have any logic specific to the Blacksky feed use cases.
The text was updated successfully, but these errors were encountered:
Fairly certain this could be a hosting provider issue but still want a good way to measure this to be sure.
When I'm running the firehose locally it seems to get all the events. What I thought was missing was because my firehose disconnected for unrelated reasons.
It's hard to diagnose but I've anecdotally noticed that during peak times (the latest user influx) there are posts that don't end up in the Blacksky feed that should (people using #AddToBlacksky, existing members, etc)
The firehose isn't getting "too-slow" errors. Issue seems to happen locally as well.
Step 1 of this would be to have a reliable way to know if messages have been missed (optimistically consuming 100% of the firehose at all times until filtering arrives).
Step 2 would be having a way to go back and get those missed messages.
Without either of these I have no way to know if folks were trying to get on Blacksky and end up having to add them manually.
Note: Firehose is generic and doesn't have any logic specific to the Blacksky feed use cases.
The text was updated successfully, but these errors were encountered: