Back to All Scenarios
PASSEDcache / dependency_timeout
KeyDB 6.3 Cannot Reach Dependency — Connection Timeout on Amazon Linux 2023
KeyDB 6.3 cannot connect to a required downstream service. All requests that depend on this connection are failing or queuing.
Pattern
TIMEOUT
Severity
HIGH
Confidence
60%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | TIMEOUT | TIMEOUT | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Amazon Linux 2023. KeyDB 6.3 configured to connect to downstream dependency. Connection timeout after 30s. Firewall rule or network partition blocking traffic. 153 users/connections requests affected.
Injected Error Messages (1)
KeyDB 6.3 on Amazon Linux 2023 — ETIMEDOUT connecting to downstream dependency, timeout after 30s, all dependent requests failing, 153 users/connections requests queued
Neural Engine Root Cause Analysis
Request timed out — service may be under heavy load, experiencing network issues, or behind a slow upstream.
Remediation Plan
Check server resource utilization (CPU/memory/disk). Investigate network path. Consider scaling if load-related.
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnqo7x07c8lig7w6xm6egr