Slow or unstable internet connectivity on the client side is one of the most common root causes of this issue.
When a client consumes messages more slowly than Stream API publishes them, the unconsumed messages are placed in a queue. As this queue grows, it can result in receiving delayed or outdated data because the client is processing older messages.
In some cases, the queue can be reduced if the client’s consumption rate increases or if Stream API publication rate decreases. However, if the queue size reaches a defined threshold, we have a mechanism that disconnects the client to prevent further impact.
Comments
0 comments
Article is closed for comments.