-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sparkmonitor failure for kernel restart - java.net.SocketException: Broken pipe (Write failed) #11
Comments
@creepysta Can you please explain the steps you took after adding that one line to the listener file? I'm new to
These jars appear in My current plan is to make the change in a separate repo and try to |
@rdhara I used github actions for building JAR files by modifying it to upload jar files as a release: https://github.com/utkarshgupta137/sparkmonitor/blob/master/.github/workflows/publish.yml#L41 |
Thank you I'll try this! |
Hi @rdhara , apologies for the late reply. Can you try |
Yup I figured it out (same step you have) and got it to work, thank you @creepysta! |
Hi,
Noticed the following issue when restarting the kernel from a classic Jupyter Notebook using JEG to launch remote spark kernels in kubernetes. The sparkmonitor doesn't show up, and in the driver logs we see its a
java.net.SocketException: Broken pipe (Write failed)
that's being thrown and the following line -[IPKernelApp] WARNING | No such comm: b5b03d3c1393459f9b736fb5f5dd5461
PFA the stack trace at the end.
Observations so far -
For a successful case -
For failure case -
For a temporary fix, to replicate the successful case, a delay of 20secs has been placed in the
CustomListener.scala
before establishing the socket connection. This is to ensure theComm opened
is done beforeClient Connected
Thanks @akhileshram for pointing out the fix
Any hint, or help with this issue will help out a lot.
Error
The text was updated successfully, but these errors were encountered: