Infrastructure Scenario Tests
We test Corax against real-world infrastructure failures across every vendor, platform, and scenario. Browse the results below.
ClickHouse 24.3 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSClickHouse 24.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ClickHouse 24.3 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream
PASSClickHouse 24.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ClickHouse 24.3 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSClickHouse 24.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ClickHouse 24.3 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSClickHouse 24.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ClickHouse 24.3 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSClickHouse 24.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
ClickHouse 24.3 Container OOM Killed — Memory Limit Hit on Amazon Linux 2023
PASSClickHouse 24.3 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
MongoDB 7.0 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSMongoDB 7.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
CockroachDB 24.1 Container OOM Killed — Memory Limit Hit on RHEL 9
PASSCockroachDB 24.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
CockroachDB 24.1 Container OOM Killed — Memory Limit Hit on Debian 12 Bookworm
PASSCockroachDB 24.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
CockroachDB 24.1 Container OOM Killed — Memory Limit Hit on Rocky Linux 9
PASSCockroachDB 24.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
CockroachDB 24.1 Container OOM Killed — Memory Limit Hit on CentOS 9 Stream
PASSCockroachDB 24.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
CockroachDB 24.1 Container OOM Killed — Memory Limit Hit on Ubuntu 24.04 LTS
PASSCockroachDB 24.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
CockroachDB 24.1 Container OOM Killed — Memory Limit Hit on Ubuntu 22.04 LTS
PASSCockroachDB 24.1 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
SQL Server 2022 Container OOM Killed — Memory Limit Hit on Windows 10 Enterprise
PASSSQL Server 2022 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
SQL Server 2022 Container OOM Killed — Memory Limit Hit on Windows 11 Enterprise
PASSSQL Server 2022 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
SQL Server 2022 Container OOM Killed — Memory Limit Hit on Windows Server 2019
PASSSQL Server 2022 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
SQL Server 2022 Container OOM Killed — Memory Limit Hit on Windows Server 2022
PASSSQL Server 2022 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
MongoDB 7.0 Container OOM Killed — Memory Limit Hit on Windows 10 Enterprise
PASSMongoDB 7.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
MongoDB 7.0 Container OOM Killed — Memory Limit Hit on Windows 11 Enterprise
PASSMongoDB 7.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
MongoDB 7.0 Container OOM Killed — Memory Limit Hit on Windows Server 2019
PASSMongoDB 7.0 running in a container was OOM killed due to exceeding its memory limit. Container restarting in a loop.
Every scenario is tested against Corax's Neural Engine in a production environment with AI-powered root cause analysis.
Tests run continuously as new infrastructure patterns are added.