[jira] [Updated] (LIVY-735) Fix RPC Channel Closed When Multi Clients Connect to One Driver
[ https://issues.apache.org/jira/browse/LIVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiheng Wang updated LIVY-735: - Summary: Fix RPC Channel Closed When Multi Clients Connect to One Driver (was: Fix RPC Channel Closed When multi clients connect to one driver ) > Fix RPC Channel Closed When Multi Clients Connect to One Driver > > > Key: LIVY-735 > URL: https://issues.apache.org/jira/browse/LIVY-735 > Project: Livy > Issue Type: Sub-task >Reporter: Yiheng Wang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LIVY-735) Fix RPC Channel Closed When multi clients connect to one driver
[ https://issues.apache.org/jira/browse/LIVY-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiheng Wang updated LIVY-735: - Summary: Fix RPC Channel Closed When multi clients connect to one driver (was: Fix RPC Channel closed when multi clients connect to one driver ) > Fix RPC Channel Closed When multi clients connect to one driver > > > Key: LIVY-735 > URL: https://issues.apache.org/jira/browse/LIVY-735 > Project: Livy > Issue Type: Sub-task >Reporter: Yiheng Wang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-735) Fix RPC Channel closed when multi clients connect to one driver
Yiheng Wang created LIVY-735: Summary: Fix RPC Channel closed when multi clients connect to one driver Key: LIVY-735 URL: https://issues.apache.org/jira/browse/LIVY-735 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-734) Support getAllSessions in Cluster
Yiheng Wang created LIVY-734: Summary: Support getAllSessions in Cluster Key: LIVY-734 URL: https://issues.apache.org/jira/browse/LIVY-734 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-733) Support Service Discovery
Yiheng Wang created LIVY-733: Summary: Support Service Discovery Key: LIVY-733 URL: https://issues.apache.org/jira/browse/LIVY-733 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LIVY-725) Support Route Request
[ https://issues.apache.org/jira/browse/LIVY-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiheng Wang updated LIVY-725: - Summary: Support Route Request (was: Support Route Request and Server Discovery) > Support Route Request > - > > Key: LIVY-725 > URL: https://issues.apache.org/jira/browse/LIVY-725 > Project: Livy > Issue Type: Sub-task >Reporter: Yiheng Wang >Assignee: mingchao zhao >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-732) A Common Zookeeper Wrapper Utility
Yiheng Wang created LIVY-732: Summary: A Common Zookeeper Wrapper Utility Key: LIVY-732 URL: https://issues.apache.org/jira/browse/LIVY-732 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-731) Session Allocation with server-session Mapping
Yiheng Wang created LIVY-731: Summary: Session Allocation with server-session Mapping Key: LIVY-731 URL: https://issues.apache.org/jira/browse/LIVY-731 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.
[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao updated LIVY-727: - Affects Version/s: 0.7.0 0.6.0 > Session state always be idle though the yarn application has been killed > after restart livy. > - > > Key: LIVY-727 > URL: https://issues.apache.org/jira/browse/LIVY-727 > Project: Livy > Issue Type: Bug >Affects Versions: 0.6.0, 0.7.0 >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Fix For: 0.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > # Set livy.server.recovery.mode=recovery, and create a session in yarn-cluster > # Restart livy,then kill the yarn application of the session. > # The session state will always be idle and never change to killed or dead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (LIVY-727) Session state always be idle though the yarn application has been killed after restart livy.
[ https://issues.apache.org/jira/browse/LIVY-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-727. -- Fix Version/s: 0.8.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull request 272 https://github.com/apache/incubator-livy/pull/272 > Session state always be idle though the yarn application has been killed > after restart livy. > - > > Key: LIVY-727 > URL: https://issues.apache.org/jira/browse/LIVY-727 > Project: Livy > Issue Type: Bug >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Fix For: 0.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > # Set livy.server.recovery.mode=recovery, and create a session in yarn-cluster > # Restart livy,then kill the yarn application of the session. > # The session state will always be idle and never change to killed or dead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (LIVY-729) Livy should not recover the killed session
[ https://issues.apache.org/jira/browse/LIVY-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-729. -- Fix Version/s: 0.8.0 Assignee: runzhiwang Resolution: Fixed Issue resolved by pull request 266 https://github.com/apache/incubator-livy/pull/266 > Livy should not recover the killed session > -- > > Key: LIVY-729 > URL: https://issues.apache.org/jira/browse/LIVY-729 > Project: Livy > Issue Type: Bug > Components: Server >Affects Versions: 0.6.0 >Reporter: runzhiwang >Assignee: runzhiwang >Priority: Major > Fix For: 0.8.0 > > Attachments: image-2019-12-18-08-56-46-925.png > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > !image-2019-12-18-08-56-46-925.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LIVY-730) Travis failed because of RSCClient instance stopped
[ https://issues.apache.org/jira/browse/LIVY-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999628#comment-16999628 ] runzhiwang commented on LIVY-730: - I'm working on it. > Travis failed because of RSCClient instance stopped > --- > > Key: LIVY-730 > URL: https://issues.apache.org/jira/browse/LIVY-730 > Project: Livy > Issue Type: Bug > Components: Tests >Affects Versions: 0.6.0 >Reporter: runzhiwang >Priority: Major > Attachments: image-2019-12-19-08-56-17-456.png > > > !image-2019-12-19-08-56-17-456.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-730) Travis failed because of RSCClient instance stopped
runzhiwang created LIVY-730: --- Summary: Travis failed because of RSCClient instance stopped Key: LIVY-730 URL: https://issues.apache.org/jira/browse/LIVY-730 Project: Livy Issue Type: Bug Components: Tests Affects Versions: 0.6.0 Reporter: runzhiwang Attachments: image-2019-12-19-08-56-17-456.png !image-2019-12-19-08-56-17-456.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
