dongjoon-hyun opened a new pull request, #747: URL: https://github.com/apache/spark-kubernetes-operator/pull/747
### What changes were proposed in this pull request? This PR aims to use virtual threads for the `SentinelManager` scheduled executor by providing a virtual thread factory. ### Why are the changes needed? - The sentinel health-check workers spend most of their time on Kubernetes API calls (network I/O), which is an ideal workload for virtual threads. - In addition, the worker threads now have meaningful names (`sentinel-0`, `sentinel-1`, ...) instead of the anonymous default (`pool-N-thread-M`), which helps thread-dump analysis. - Note on behavior change: the workers change from non-daemon platform threads to daemon virtual threads (virtual threads are always daemon). This does not affect JVM liveness in practice because the operator process is kept alive by the `com.sun.net.httpserver` dispatcher thread (non-daemon) and the Java Operator SDK threads. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Fable 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]
