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
Describe the bug
My kafka topic receives about 10 million+ events per day. Each message has key and there are about 50k unique keys. I have zilla sse endpoint which filters based on key. After about a day, it makes only about sse 20k sse connections. Then sometime in day 2 or later, it stops sending live updates to sse client. That is, it freezes somehow. It just show one entries. Even though additional entries are pushed, I don't get them. I'm not sure if it's cache or resource issue.
To Reproduce
Steps to reproduce the behavior:
Use similar config as mine
Send lots of events in kafka topic
Create a several thousand sse connection
At some point, you'll see zilla stops sending updates
Expected behavior
Zilla should repeatedly clean cache to outcome if it's memory issue.
Screenshots
If applicable, add screenshots to help explain your problem.
Zilla Environment:
container and resources look like
Describe the bug
My kafka topic receives about 10 million+ events per day. Each message has key and there are about 50k unique keys. I have zilla sse endpoint which filters based on key. After about a day, it makes only about sse 20k sse connections. Then sometime in day 2 or later, it stops sending live updates to sse client. That is, it freezes somehow. It just show one entries. Even though additional entries are pushed, I don't get them. I'm not sure if it's cache or resource issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Zilla should repeatedly clean cache to outcome if it's memory issue.
Screenshots
If applicable, add screenshots to help explain your problem.
Zilla Environment:
container and resources look like
Kafka Environment:
Confluent Kafka
Client Environment:
Chrome browser latest or any other browser
The text was updated successfully, but these errors were encountered: