Description
Follows are steps to reproduce the problem:
- Set livy.server.recovery.mode=recovery, and create a session: session0 in yarn-cluster
- kill the yarn application of the session
- restart livy
- livy try to recover session0, but application has been killed and driver does not exist, so client can not connect to driver, and exception was thrown as the image.
- If the ip:port of the driver was reused by session1, client of session0 will try to connect to driver of session1, then driver will throw exception: Unexpected client ID.
- Both the exception threw by livy and driver will confused the user, and recover a lot of killed sessions will delay the recover of alive session.
Attachments
Attachments
Issue Links
- links to