Shall we start an official vote before creating the subtasks? Thanks, Marco
Il giorno mer 11 dic 2019 alle ore 14:50 Saisai Shao <[email protected]> ha scritto: > I think it is feasible to move to next step. Let's create subtasks to track > all the works. > > Thanks > Saisai > > Yiheng Wang <[email protected]> 于2019年12月10日周二 下午3:18写道： > > > Hi Community > > > > We have received some feedback for this design. Here're the open > questions > > for discussion > > 1. Session allocation algorithm > > We agree to make it pluggable. There're two allocation algorithms: > > server-session mapping and consistent hashing. We haven't agreed on which > > one is the default. > > 2. The semantic change of getAllSessions > > We agree to not change its semantics. However, we haven't achieved > > an agreement on the implementation. > > > > We think the open questions are not a blocker. So can we have this design > > doc approved? > > > > Thanks > > Yiheng > > > > On Thu, Nov 28, 2019 at 6:37 PM Yiheng Wang <[email protected]> wrote: > > > > > Hi Community > > > > > > We propose a multi-active high availability design for Livy. We think > > this > > > feature is valuable for many users. Here're the JIRA and the design > doc. > > If > > > you're interested, please take a look and comment :-) > > > > > > JIRA: > > > https://issues.apache.org/jira/projects/LIVY/issues/LIVY-718 > > > > > > Design doc: > > > > > > > > > https://docs.google.com/document/d/1bD3qYZpw14_NuCcSGUOfqQ0pqvSbCQsOLFuZp26Ohjc/edit?usp=sharing > > > > > > Best regards > > > Yiheng > > > > > >
