arham0254A commented on issue #56539: URL: https://github.com/apache/spark/issues/56539#issuecomment-4784089688
Hi, I recently picked this up to investigate and opened a draft PR, but after tracing the control flow and testing locally, it appears the core Scala code is already returning a failure code correctly. In SparkSubmitArguments.scala, the handleUnknown method calls error(). This function throws a SparkException. Because SparkSubmit.main only catches SparkUserAppException, the SparkException remains uncaught, crashing the JVM and inherently returning an OS exit code of 1. If you are seeing an exit code of 0 after an unrecognized argument, the error is likely being swallowed by an external execution wrapper. Are you running spark-submit inside a specific orchestration tool (like Apache Airflow), a CI/CD pipeline, a Docker container, or a custom wrapper script? Could you provide the exact execution environment and the raw command being used to reproduce the 0 exit code? -- 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]
