MOBIN-F opened a new pull request #3523: [ZEPPELIN-4326][spark]Spark Interpreter restart failed when no suffic… URL: https://github.com/apache/zeppelin/pull/3523 ### What is this PR for? The pr is the last fix of the [ZEPPELIN-4326](https://issues.apache.org/jira/browse/ZEPPELIN-4326) The user can still restart the spark interpreter successfullywhen no sufficient yarn queue resources When the queue resource is insufficient, the spark task will remain in the ACCEPTED state. If the spark interpreter is restarted at this time, the restart interface will be stuck[**thread blocking in the LazyOpenInterpreter.open method, this is a synchronized method**]. Restarting the spark interpreter fails. only use the yarn applicaiton -kill appID command or the kill -9 SparkSubmit process to restart the spark interpreter., which is very unfriendly to the user. At present, I use the system.exit(1) rough way to exit the JVM to achieve the purpose of restarting successfully, similar to the task of ending the ACCEPTED state by using Ctrl+C in the spark-shell. ### What type of PR is it? Bug Fix ### Todos * [ ] - Task ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-4326 ### How should this be tested? * Manually tested ### Screenshots (if appropriate)  ### Questions: * Add another ACCETTED state to tell the user that the task is in the ACCEPTED state instead of the running state?【PENDING -> ACCEPTED -> RUNNING】
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
