You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@livy.apache.org by Yiheng Wang <yi...@gmail.com> on 2019/12/10 07:18:37 UTC
Re: Support multi-active high availability in Livy
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 <yi...@gmail.com> 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
>
Re: Support multi-active high availability in Livy
Posted by Saisai Shao <sa...@gmail.com>.
As I remembered we don't have such requirement in Livy community, but I'm
OK to start a vote. Yiheng, would you please start a vote?
Thanks
Saisai
Marco Gaido <ma...@gmail.com> 于2019年12月12日周四 上午2:50写道：
> Shall we start an official vote before creating the subtasks?
>
> Thanks,
> Marco
>
> Il giorno mer 11 dic 2019 alle ore 14:50 Saisai Shao <
> sai.sai.shao@gmail.com>
> 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 <yi...@gmail.com> 于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 <yi...@gmail.com> 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
> > > >
> > >
> >
>
Re: Support multi-active high availability in Livy
Posted by Marco Gaido <ma...@gmail.com>.
Shall we start an official vote before creating the subtasks?
Thanks,
Marco
Il giorno mer 11 dic 2019 alle ore 14:50 Saisai Shao <sa...@gmail.com>
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 <yi...@gmail.com> 于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 <yi...@gmail.com> 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
> > >
> >
>
Re: Support multi-active high availability in Livy
Posted by Saisai Shao <sa...@gmail.com>.
I think it is feasible to move to next step. Let's create subtasks to track
all the works.
Thanks
Saisai
Yiheng Wang <yi...@gmail.com> 于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 <yi...@gmail.com> 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
> >
>