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
In a finite streaming dataset, Receive drops the last x UDP messages. It seems likely that it's batching messages and waits infinitely to fill up the last batch.
AC
Receive does not drop messages on the tail of the dataset
Updated for clarity. We saw this tail drop on UDP messages, not websockets. See notes for more info. It may not be a timeout/batching thing, but it is consistently dropping messages on the tail of the dataset.
I would still focus debugging on the shutdown of the process; UDP also has a built in timeout and there's a test that has been consistently passing for months that verifies that an incomplete batch is sent if the timeout is reached.
In a finite streaming dataset, Receive drops the last x UDP messages. It seems likely that it's batching messages and waits infinitely to fill up the last batch.
AC
Tech Notes
The text was updated successfully, but these errors were encountered: