[
https://issues.apache.org/jira/browse/LIVY-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-719:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> 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
> Fix For: 0.10.0
>
>
> 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.20.10#820010)
