You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a SparkConf is invalid for launching our engines, it is better to fail fast instead of waiting for Spark to check while engine bootstrapping.
Motivation
Save time to create an invalid engine
Avoid possible hang
better error message
Here is an example I did for Spark to validate its own configs when talking to Kubernetes. apache/spark#32610
Task list
Generally speaking, we can have 1) a tool in kyuubi-ctl to check server/engine conf in configuration files are valid, 2) The logic of the tool can also be called when engine bootstrapping for the configurations from the client side
Describe the proposal
When a SparkConf is invalid for launching our engines, it is better to fail fast instead of waiting for Spark to check while engine bootstrapping.
Motivation
Here is an example I did for Spark to validate its own configs when talking to Kubernetes. apache/spark#32610
Task list
Generally speaking, we can have 1) a tool in
kyuubi-ctl
to check server/engine conf in configuration files are valid, 2) The logic of the tool can also be called when engine bootstrapping for the configurations from the client sidespark.kubernetes.executor.podNamePrefix
is invalid #833The text was updated successfully, but these errors were encountered: