Uploaded image for project: 'Livy'
  1. Livy
  2. LIVY-729

Livy should not recover the killed session

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.6.0
    • 0.8.0
    • Server
    • None

    Description

      Follows are steps to reproduce the problem:

      1. Set livy.server.recovery.mode=recovery, and create a session: session0 in yarn-cluster
      2. kill the yarn application of the session
      3. restart livy
      4. 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.
      5. 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.
      6. 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

        Issue Links

          Activity

            People

              runzhiwang Jie Wang
              runzhiwang Jie Wang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m