HTTP GOAWAY frame from worker under high load
I am connecting to a worker via HTTP2. When I’m sending lots of events via the same connection (but not more than 50-100 events per second) I keep getting a GOAWAY frame after a while.
I’d love to know the reason for this so I can decide how to handle it.
- just maintenance on your side? (but it feels to me like its load connected)
- some DDoS protection? (but 100 events per second seems low)
- routinely asking to recycle the connection after x events?
I’d also like to know whether you’re passing additional information like error code, last stream Id etc in the frame. If so we’d need to move to a lower level http client to take advantage of this information.
Thanks!
0 Replies