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
I was trying install some custom logic which basically performs rate limit with buffering. The logic looks like this: let's say we want limit the rate to 1/delay. Each worker thread maintains it own queue, a global shared data records the timeout of the last elements in the queues across all worker threads. Every time a http request comes in, it will be paused. Its contextID will be pushed into a queue with a timeout=shared_timeout+delay. The thread will periodically call ticker function to resume the execution of requests with passed timeout.
When I was running this with online-boutique, there are some crashes in the worker threads.
Crash in frontend pod which accepts incoming HTTP/1.1 requests
Crash in other pods which accepts incoming gRPC calls. This happens mostly during the end of experiments. Not sure if it's because envoy tries to resume the http requests while the connection is closed.
Describe the bug / error
I was trying install some custom logic which basically performs rate limit with buffering. The logic looks like this: let's say we want limit the rate to 1/delay. Each worker thread maintains it own queue, a global shared data records the timeout of the last elements in the queues across all worker threads. Every time a http request comes in, it will be paused. Its contextID will be pushed into a queue with a timeout=shared_timeout+delay. The thread will periodically call ticker function to resume the execution of requests with passed timeout.
When I was running this with online-boutique, there are some crashes in the worker threads.
What is your Envoy/Istio version?
1.17.1
What is the SDK version?
latest repo with commit 19b7668
What is your TinyGo version?
0.27.0
URL or snippet of your code including Envoy configuration
enovyfilter yaml
Additional context (Optional)
The text was updated successfully, but these errors were encountered: