dongjoon-hyun opened a new pull request, #952:
URL: https://github.com/apache/spark-kubernetes-operator/pull/952

   ### What changes were proposed in this pull request?
   
   This PR aims to suspend a running `SparkApplication` whose Kueue `Workload` 
is evicted or deactivated, and to queue it again with a new attempt, like a 
running `SparkCluster`.
   
   - `AppSuspendStep` moves such an application to `Suspended` and releases its 
driver and executors. Then it deletes the `Workload` after the requeue backoff, 
or keeps a deactivated one until it is reactivated.
   - The new attempt starts with `ApplicationStatus#resume`, so it does not 
count as a restart.
   - A `PodsReadyTimeout` is handled like any other eviction, and 
`spec.suspend` takes precedence.
   - `AppKueueEvictionStep` and the `KueueEvictionIgnored` event are removed.
   
   ### Why are the changes needed?
   
   Currently, the driver and executors keep running after an eviction. So 
preemption, cohort quota reclamation and `waitForPodsReady` do not work, and a 
deactivated `Workload` over-commits the quota.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No for the released versions, because the Kueue integration is not released 
yet in 
[1.0.0](https://github.com/apache/spark-kubernetes-operator/releases/tag/1.0.0) 
(2026-07-23).
   
   ### 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 Opus 5.5


-- 
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]

Reply via email to