-
Notifications
You must be signed in to change notification settings - Fork 1.3k
APM: Reduce likelihood of receiver shutdown panic #37832
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
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: f78cfdf Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +2.10 | [+1.25, +2.94] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.75 | [+0.57, +0.94] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.59 | [+0.45, +0.73] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.51 | [+0.44, +0.59] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_logs | % cpu utilization | +0.51 | [-2.24, +3.27] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | +0.45 | [+0.31, +0.60] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.34 | [+0.28, +0.40] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.19 | [+0.13, +0.25] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.07 | [-0.01, +0.14] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.02] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.00 | [-0.60, +0.61] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.01 | [-0.62, +0.60] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.02 | [-0.30, +0.27] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.03 | [-0.68, +0.63] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.05 | [-0.28, +0.19] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.06 | [-0.63, +0.52] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.07 | [-0.65, +0.52] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.08 | [-0.70, +0.53] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.09 | [-0.68, +0.49] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.19 | [-0.30, -0.07] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.20 | [-0.32, -0.07] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.49 | [-0.58, -0.40] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -0.69 | [-3.68, +2.30] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM FWIW
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Move our usage of waitgroup to cover the entire
process
function to ensure that the Stop() function doesn't close theout
channel until we've processed all payloadsMotivation
This should reduce the incidence of panics during shutdown
Describe how you validated your changes
I ran this locally with a test tracer to ensure it still functions correctly and saw it was successful. I also attempted to recreate the
send after close
panic (before and after) and could not do so locally.Possible Drawbacks / Trade-offs
This does not fully resolve this issue, there is still a narrow window in which this issue can still occur. I have been unable to identify the underlying issue that is causing server.Shutdown() to not block until all handlers return, so this is a stop-gap measure to reduce incidence while continuing investigation.
The use of a wait group here for ever incoming trace payload will incur a very small performance cost.
Additional Notes