DanielLeens opened a new pull request, #494: URL: https://github.com/apache/seatunnel-website/pull/494
## What changed - Updated the SeaTunnel 2.3.13 separated cluster deployment examples for both Master and Worker nodes from a 2 GB JVM heap to a 16 GB JVM heap. - Updated the 2.3.13 Kubernetes Zeta cluster example to use a 16 GB heap, a 20 GiB memory request, and a 24 GiB memory limit. - Corrected the Kubernetes shell quoting so both `-Xms` and `-Xmx` are passed through one `JvmOption` argument. - Added a 32 GB JVM heap recommendation for large-scale data processing, with example Kubernetes request/limit values of 36 GiB and 40 GiB. - Kept the English and Chinese versioned documentation consistent. ## Why The 2.3.13 versioned documentation should provide the same practical JVM heap sizing guidance as the current SeaTunnel documentation, including runnable Kubernetes examples. ## User impact Users reading the 2.3.13 deployment and Kubernetes guides will see updated heap sizing examples and the large-scale workload recommendation. This documentation-only change does not alter runtime defaults. ## Validation - `git diff --check` - Parsed the affected Kubernetes YAML examples. - Verified matching `-Xms16g` and `-Xmx16g` values in both Master and Worker examples. - Verified the Kubernetes command passes both heap options through one `JvmOption` argument. - Verified the English and Chinese documents contain the same 32 GB recommendation. - 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]
