DanielLeens opened a new pull request, #495:
URL: https://github.com/apache/seatunnel-website/pull/495
## What changed
- Updated the SeaTunnel 2.3.13 Kubernetes Zeta cluster example from a
one-CPU container to:
- CPU request: 4
- CPU limit: 8
- Added a large-scale starting point for a 32 GB JVM heap:
- CPU request: 8
- CPU limit: 16
- Memory request/limit: 36 GiB/40 GiB
- Kept the English and Chinese versioned documentation consistent.
## Why
The previous one-CPU limit was unbalanced with the documented 16 GB JVM
heap. Task execution, garbage collection, Hazelcast, and engine coordination
threads would compete for one CPU, causing throttling and avoidable throughput
or latency instability.
## User impact
Users reading the 2.3.13 Kubernetes guide receive a practical CPU and memory
starting point. The guide also states that production values should be adjusted
using connector characteristics, job parallelism, and observed CPU, GC, and
memory utilization.
This documentation-only change does not alter runtime or Helm chart defaults.
## Validation
- `git diff --check`
- Parsed all YAML blocks in both affected MDX documents.
- Verified matching CPU request/limit values of 4/8 in English and Chinese.
- Verified matching large-scale CPU and memory guidance of 8/16 and 36/40
GiB.
- Verified Markdown/MDX code fences remain balanced.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
