dongjoon-hyun opened a new pull request, #58582: URL: https://github.com/apache/spark/pull/58582
### What changes were proposed in this pull request? This PR aims to add a configurable upper bound to `ExecutorResizePlugin`. | Config | Default | |---|---| | `spark.kubernetes.executor.resizeMaxMemory` | `Long.MaxValue` (no upper bound) | When the computed new memory limit exceeds the cap, it is clamped to the cap. When the current limit is already at or above the cap, the resize is skipped and an INFO message is logged once per executor instead of on every interval. This is a sub-task of SPARK-55555 (Support heterogeneous K8s executor management). ### Why are the changes needed? `ExecutorResizePlugin` currently only grows the executor container memory limit with no maximum. As long as usage stays above the threshold, the limit keeps growing without bound. An upper bound lets users adopt the plugin safely with a predictable worst-case memory footprint. ### Does this PR introduce _any_ user-facing change? No. The new config defaults to `Long.MaxValue`, so the existing behavior is unchanged unless a user sets it. ### How was this patch tested? Pass the CIs with newly added test cases. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Fable 5.1 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
