+1 Best regards, Aliaksandr Sasnouskikh https://github.com/jahstreet/ https://www.linkedin.com/in/jahstreet/ +31 (0) 6 51 29 58 39
чт, 12 дек. 2019 г. в 07:24, Saisai Shao <[email protected]>: > +1 > > rei sivan <[email protected]> 于2019年12月12日周四 下午2:09写道： > > > +1 > > > > On Thu, Dec 12, 2019, 05:30 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 > > > > > >
