dongjoon-hyun opened a new pull request, #58583: URL: https://github.com/apache/spark/pull/58583
### What changes were proposed in this pull request? This PR aims to add a configurable upper bound to `ExecutorPVCResizePlugin` so that the PVC storage request cannot grow beyond a given size. | Config | Default | | --- | --- | | `spark.kubernetes.executor.pvc.resizeMaxStorage` | `Long.MaxValue` (no upper bound) | - When the computed new storage request (`current * (1 + resizeFactor)`) exceeds the cap, it is clamped to the cap. - When the current storage request is already at or above the cap, the resize is skipped and an INFO message is logged once per PVC. This is a sub-task of SPARK-55555 (Support heterogeneous K8s executor management). ### Why are the changes needed? Currently, the plugin only grows the PVC storage request by `resizeFactor` whenever the usage ratio exceeds the threshold, with no maximum. An upper bound gives users a predictable worst-case storage footprint per executor PVC. ### Does this PR introduce _any_ user-facing change? No. The new config defaults to `Long.MaxValue`, which preserves the existing behavior. ### How was this patch tested? Pass the CIs with the 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]
