This is a long-standing problem .
If we have a Spark session (SW) connected to H2O (backend cluster), and then cluster restarts,
it fails that spark sessions (or multiple spark sessions ) even though they may not need
H2O / SW functionality for some downstream processing.
All users are currently forced to restart their Spark sessions, again even though they don't need
SW / H2O connectivity.
This issue always reproduces for us.
error when this happens.
It would be nice if shutting down the H2O cluster didn’t result in an error for all H2O connected users.