dongjoon-hyun opened a new pull request, #56511: URL: https://github.com/apache/spark/pull/56511
### What changes were proposed in this pull request? This PR removes the standalone `Master` check that rejects `spark.authenticate.secret` when the Master REST server (`spark.master.rest.enabled`) is enabled. ### Why are the changes needed? `spark.authenticate.secret` (the RPC authentication secret) and `spark.master.rest.enabled` (the standalone submission REST server) are independent concerns, but the removed check coupled them by failing Master startup whenever both were set. Since `spark.master.rest.enabled` defaults to `true` (SPARK-51165), this forced any cluster using RPC authentication to also disable the REST server. The REST endpoint can still be turned off independently via `spark.master.rest.enabled=false`. ### Does this PR introduce _any_ user-facing change? Yes. Previously, starting a standalone Master with `spark.authenticate.secret` set and `spark.master.rest.enabled=true` (the default) failed with an `IllegalArgumentException`. After this PR, the Master starts normally with both configured. ### How was this patch tested? Added a unit test in `MasterSuite` that verifies a `Master` can be created with both `spark.master.rest.enabled=true` and `spark.authenticate.secret` set. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) -- 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]
