|
|
|
SPARK-42699
|
SPARK-36623
SparkConnectServer should make client and AM same exit code
|
Unassigned
|
angerszhu
|
|
In Progress |
Unresolved
|
|
|
|
|
|
|
|
SPARK-42698
|
SPARK-36623
Client mode submit task client should keep same exitcode with AM
|
Unassigned
|
angerszhu
|
|
In Progress |
Unresolved
|
|
|
|
|
|
|
|
SPARK-38270
|
SPARK-36623
SQL CLI AM should keep same exitcode with client
|
angerszhu
|
angerszhu
|
|
Resolved |
Fixed
|
|
|
|
|
|
|
|
SPARK-37097
|
SPARK-36623
yarn-cluster mode, unregister timeout cause spark retry but AM container exit with code 0
|
Unassigned
|
angerszhu
|
|
In Progress |
Unresolved
|
|
|
|
|
|
|
|
SPARK-36691
|
SPARK-36623
PythonRunner failed should pass error message to ApplicationMaster too
|
Unassigned
|
angerszhu
|
|
In Progress |
Unresolved
|
|
|
|
|
|
|
|
SPARK-36650
|
SPARK-36623
ApplicationMaster shutdown hook should catch timeout exception
|
angerszhu
|
angerszhu
|
|
Resolved |
Fixed
|
|
|
|
|
|
|
|
SPARK-36624
|
SPARK-36623
When application killed, sc should not exit with code 0
|
angerszhu
|
angerszhu
|
|
Resolved |
Fixed
|
|
|
|
|
|
|
|
SPARK-36615
|
SPARK-36623
SparkContext should register shutdown hook earlier
|
angerszhu
|
angerszhu
|
|
Resolved |
Fixed
|
|
|
|
|
|
|
|
SPARK-36540
|
SPARK-36623
AM should not just finish with Success when dissconnected
|
angerszhu
|
angerszhu
|
|
Resolved |
Fixed
|
|
|
|
|