[jira] [Commented] (LIVY-725) Support Route Request and Server Discovery
[ https://issues.apache.org/jira/browse/LIVY-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985798#comment-16985798 ] mingchao zhao commented on LIVY-725: I'm working on this part > Support Route Request and Server Discovery > -- > > 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] [Assigned] (LIVY-725) Support Route Request and Server Discovery
[ https://issues.apache.org/jira/browse/LIVY-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mingchao zhao reassigned LIVY-725: -- Assignee: mingchao zhao > Support Route Request and Server Discovery > -- > > 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-725) Support Route Request and Server Discovery
Yiheng Wang created LIVY-725: Summary: Support Route Request and Server Discovery Key: LIVY-725 URL: https://issues.apache.org/jira/browse/LIVY-725 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-724) Support Server Leave/Join and Session Cross Server Recovery
Yiheng Wang created LIVY-724: Summary: Support Server Leave/Join and Session Cross Server Recovery Key: LIVY-724 URL: https://issues.apache.org/jira/browse/LIVY-724 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-723) Server Registration
Yiheng Wang created LIVY-723: Summary: Server Registration Key: LIVY-723 URL: https://issues.apache.org/jira/browse/LIVY-723 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-722) Session Allocation with Consistent Hashing
Yiheng Wang created LIVY-722: Summary: Session Allocation with Consistent Hashing Key: LIVY-722 URL: https://issues.apache.org/jira/browse/LIVY-722 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LIVY-721) Distributed Session ID Generation
[ https://issues.apache.org/jira/browse/LIVY-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiheng Wang updated LIVY-721: - Summary: Distributed Session ID Generation (was: Distributed Session ID generation) > Distributed Session ID Generation > - > > Key: LIVY-721 > URL: https://issues.apache.org/jira/browse/LIVY-721 > 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-721) Distributed Session ID generation
Yiheng Wang created LIVY-721: Summary: Distributed Session ID generation Key: LIVY-721 URL: https://issues.apache.org/jira/browse/LIVY-721 Project: Livy Issue Type: Sub-task Reporter: Yiheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LIVY-719) Livy is not high available in aws EMR cluster
[ https://issues.apache.org/jira/browse/LIVY-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985791#comment-16985791 ] Yiheng Wang commented on LIVY-719: -- Hi We have proposed a JIRA for Livy HA. https://issues.apache.org/jira/browse/LIVY-718 > Livy is not high available in aws EMR cluster > - > > Key: LIVY-719 > URL: https://issues.apache.org/jira/browse/LIVY-719 > Project: Livy > Issue Type: Bug >Reporter: chiranjeevi patel >Priority: Major > > Hi, > We have been using the Livy in our EMR cluster to submit the batch jobs, now > after upgrading to EMR 5.0.24 with multi master capability, livy is not able > to handle the sessions on master failover. > Livy is installed on all three master nodes and running as independent > application, so a master node failure is bringing down the livy session, > where EMR was abel to switch the active master to standby one, but out jobs > were failing, since we lost the session with previous active master, and we > need to explicitly connect to the new active master with a different IP. > > Do you have any plans to support multi master (HA) clusters ? > I have asked the AWS support team, and they responded as livy is due with > many open source issues, and they can work on it only when these issues are > sorted. > Let me know if you need any further details > -- This message was sent by Atlassian Jira (v8.3.4#803005)
