cloud-fan opened a new pull request, #57854: URL: https://github.com/apache/spark/pull/57854
### What changes were proposed in this pull request? Followup to https://github.com/apache/spark/pull/56907. This change hardens persistent local Spark Connect server management in two ways. Before sending SIGTERM, the client verifies that the PID recorded in discovery still belongs to SparkConnectServer. The launcher also removes inherited binding-address configuration and explicitly binds the server to 127.0.0.1. ### Why are the changes needed? A stale discovery file can refer to a PID that the operating system has reused for an unrelated process. Signaling that process would be unsafe. Separately, an inherited binding-address setting can expose a server that is intended to remain local. ### Does this PR introduce _any_ user-facing change? No. The persistent local server remains opt-in. The change only makes its shutdown and network binding behavior safer. ### How was this patch tested? Added regression tests that verify a reused PID is not signaled and that the launcher forces the loopback binding address. The complete PySpark Connect test environment will be run before the staged proposal is published as an OSS PR. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-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]
