Sorry for coming late to this thread. I have put my comments on the jira ticket here - https://issues.apache.org/jira/browse/LIVY-718?focusedCommentId=17004728&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17004728
It would be nice if we could consider the issues raised in the comments and see if it makes sense to accommodate for those in the design proposal. Thanks Bikas ________________________________ From: Marco Gaido <[email protected]> Sent: Wednesday, December 18, 2019 10:52 PM To: [email protected] <[email protected]> Subject: Re: [RESULT][Vote][LIVY-718] Support multi-active high availability in Livy Thank you for this proposal and your work. Looking forward to it. Thanks, Marco On Thu, 19 Dec 2019, 07:27 Yiheng Wang, <[email protected]> wrote: > Hi All > > Thanks for participating in the vote. Here's the result: > +1 (binding) > ajbozarth > zjffdu > mgaido91 > jerryshao > > +1 (no-binding) > 5 > > The vote passes. I will create subtasks for it. > > Thanks > Yiheng > > On Thu, Dec 12, 2019 at 11:30 AM Yiheng Wang <[email protected]> wrote: > > > Dear Community > > > > I'd like to call a vote on LIVY-718 > > <https://issues.apache.org/jira/projects/LIVY/issues/LIVY-718> "Support > > multi-active high availability in Livy". > > > > Currently, Livy only supports single node recovery. This is not > sufficient > > in some production environments. In our scenario, the Livy server serves > > many notebook and JDBC services. We want to make Livy service more > > fault-tolerant and scalable. > > > > There're already some proposals in the community for high availability. > > But they're not so complete or just for active-standby high availability. > > So we propose a multi-active high availability design to achieve the > > following goals: > > > > - One or more servers will serve the client requests at the same time. > > - Sessions are allocated among different servers. > > - When one node crashes, the affected sessions will be moved to other > > active services. > > > > Please find the design doc here > > < > https://docs.google.com/document/d/1bD3qYZpw14_NuCcSGUOfqQ0pqvSbCQsOLFuZp26Ohjc/edit?usp=sharing > >, > > which has been reviewed for several weeks. > > > > This vote is open until next Wednesday (Dec. 18). > > > > [] +1: Accept the proposal > > [] +0 > > [] -1: I don't think this is a good idea because ... > > > > Thank you > > > > Yiheng > > >
