New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Envoy::Router::PrefixRouteEntryImpl::matches() Caught Segmentation fault, suspect faulting address #590
Comments
looking at the code its hard to see what can be the issue - let me get a new version of envoy-gloo compiled against latest upstream, and then would you mind testing again? |
yes sure |
what envoy was this? the one from gloo open source? or gloo enterprise |
gloo open souce Envoy version: b696ded71901e11cf4b83fb547fe4f7e5a2fdba0/1.10.0-dev/Distribution/RELEASE/BoringSSL |
FYI might be helpful
|
i was able to reproduce this; debugging |
@benishak See the root cause here: envoyproxy/envoy#6348 (comment) |
Thanks a lot! looking forward for the fix to be released. |
fix in envoyproxy/envoy#6359 |
i'm incorporating the change into envoy-gloo and will release it soon |
awesome, is it part of 0.13 release? |
didnt make it to 0.13, it will be part of 0.13.1, which i will create promptly. |
fixed by #607 |
Bug Template
envoyproxy/envoy#6348
Title: One line description
Description:
I try to run Envoy on AWS EC2 c5n.9xlarge with Gloo on Kubernetes,
I run it on production to serve 2,000,000+ RPM (http+https)
after running it for 10min, it crashed.
I have 2 listeners
both are configured with the following routers
gloo version: 0.11.2
Envoy version: b696ded71901e11cf4b83fb547fe4f7e5a2fdba0/1.10.0-dev/Distribution/RELEASE/BoringSSL
Repro steps:
Configure Envoy with 2 listeners and use similar routing like above and try to send it 200000 RPM/m for 10min+
Call Stack:
CPU and Load were fine during the run
But I noticed high DIsk Write IO around 5GB before it crashed and disk usage jumped from 2GB to 9.6GB out of total 20GB
Memory usage peak was around 15GB
This instance has around 92GB RAM and 36 Cores
The text was updated successfully, but these errors were encountered: