jiangzho opened a new pull request, #513: URL: https://github.com/apache/spark-kubernetes-operator/pull/513
### What changes were proposed in this pull request? This PR adds a new `RunningWithPartialCapacity` state to `ApplicationStateSummary` that indicates when a Spark application with dynamic allocation disabled is running with executor count between minimum and maximum thresholds. ### Why are the changes needed? When dynamic allocation is disabled, if an application has fewer executors than requested (between min and max), it indicates resource constraints in the cluster. This is a tolerable but suboptimal state that should be visible to operators. With dynamic allocation enabled, executors scaling between min and max is normal behavior, so `RunningHealthy` is appropriate. The new state provides better observability into cluster resource constraints affecting application performance. ### Does this PR introduce _any_ user-facing change? Yes. Users will now see `RunningWithPartialCapacity` status for applications. ### How was this patch tested? Added unit tests in `AppRunningStepTest` covering state transition with different number of executors. Also added unit tests in `ApplicationStateSummaryTest` verifying the new state summary. ### Was this patch authored or co-authored using generative AI tooling? No -- 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]
