Started by GitHub push by ti-chi-bot[bot]00167751677551904519041.02541225412077316863686361342e1f9d7bcc721b6a2927c2111bf2912deef9172a0e1f9d7bcc721b6a2927c2111bf2912deef9172a0origin/maine1f9d7bcc721b6a2927c2111bf2912deef9172a0e1f9d7bcc721b6a2927c2111bf2912deef9172a0origin/maine1f9d7bcc721b6a2927c2111bf2912deef9172a0e1f9d7bcc721b6a2927c2111bf2912deef9172a0origin/mainhttps://github.com/PingCAP-QE/ci.githttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1342/artifactshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1342/changeshttps://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1342/https://do.pingcap.net/jenkins/blue/organizations/jenkins/seed/detail/seed/1342/testsfalse#13425190486474seed #13421342falsefalse13423003787SUCCESS1768362887486https://do.pingcap.net/jenkins/view/all/job/seed/1342/default-8h3kq- pipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy/pod-test.yamlpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pod.yamlpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pod.yamlpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light/pod-test.yamlpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light/pod-test.yamlpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pod-test.yamle1f9d7bcc721b6a2927c2111bf2912deef9172a01768362847000https://do.pingcap.net/jenkins/user/noreplynoreplynoreply@github.comTiCDC: Increase memory limits for TiCDC integration test pods to improve stability (#4090)
## Increase Memory Limits for TiCDC Integration Test Pipelines
This PR updates the memory resource limits for several TiCDC integration
test pipelines to improve stability and prevent out-of-memory (OOM)
failures during test execution.
### Why this change?
Recent test runs have shown intermittent failures due to memory
exhaustion, particularly in heavier integration scenarios. Increasing
the memory allocation ensures tests have sufficient resources to
complete reliably, reducing flakiness and improving overall CI/CD
pipeline stability.
### Changes Made:
- **Kafka Integration Light Tests**: Memory increased from 8Gi to 16Gi
for both `pull_cdc_kafka_integration_light` and
`pull_cdc_kafka_integration_light_next_gen`.
- **MySQL Integration Heavy Tests**: Memory increased from 16Gi to 32Gi
for both `pull_cdc_mysql_integration_heavy` and
`pull_cdc_mysql_integration_heavy_next_gen`.
- **Storage Integration Light Tests**: Memory increased from 8Gi to 16Gi
for both `pull_cdc_storage_integration_light` and
`pull_cdc_storage_integration_light_next_gen`.
### Impact:
- CPU limits remain unchanged across all pipelines.
- These adjustments align with observed resource usage patterns and are
expected to eliminate OOM-related test failures without
over-provisioning.
---------
Signed-off-by: tenfyzhong <tenfy@tenfy.cn>
Co-authored-by: wuhuizuo <wuhuizuo@126.com>
2026-01-14 03:54:07 +0000e1f9d7bcc721b6a2927c2111bf2912deef9172a0TiCDC: Increase memory limits for TiCDC integration test pods to improveeditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light_next_gen/pod-test.yamleditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light_next_gen/pod.yamleditpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy/pod-test.yamleditpipelines/pingcap/ticdc/latest/pull_cdc_mysql_integration_heavy_next_gen/pod.yamleditpipelines/pingcap/ticdc/latest/pull_cdc_kafka_integration_light/pod-test.yamleditpipelines/pingcap/ticdc/latest/pull_cdc_storage_integration_light/pod-test.yaml
githttps://do.pingcap.net/jenkins/user/noreplynoreplynoreply