+1
Alex Bozarth
Software Engineer
Center for Open-Source Data & AI Technologies
E-mail: ajboz...@us.ibm.com
GitHub: github.com/ajbozarth
505 Howard
Street
San Francisco, CA
94105
United
States
From: Yiheng Wang <yihe...@gmail.com>
To: dev <dev@livy.incubator.apache.org>
Date: 12/11/2019 07:30 PM
Subject: [EXTERNAL] [Vote][LIVY-718] Support multi-active high
availability in Livy
Dear Community
I'd like to call a vote on LIVY-718
<
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_projects_LIVY_issues_LIVY-2D718&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=qEwwh1ZzyvlfhzNhTXIHy8JaVEhc8Ynca3UuwxOzbu0&s=u5gOYOhyET-GoBtWvEMeXcWCoIFDwqqb6yY0_yMNA44&e=
> "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://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1bD3qYZpw14-5FNuCcSGUOfqQ0pqvSbCQsOLFuZp26Ohjc_edit-3Fusp-3Dsharing&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=qEwwh1ZzyvlfhzNhTXIHy8JaVEhc8Ynca3UuwxOzbu0&s=TE5uI9hb0M_9UHcTVaIzuPNMe6vAExOlPqqJv5rfYzw&e=
>,
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
