Re: [RESULT][Vote][LIVY-718] Support multi-active high availability in Livy

[Marco Gaido]

Thank you for this proposal and your work. Looking forward to it.
Thanks,
Marco

On Thu, 19 Dec 2019, 07:27 Yiheng Wang,  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  wrote:
>
> > Dear Community
> >
> > I'd like to call a vote on 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
> >
>

[RESULT][Vote][LIVY-718] Support multi-active high availability in Livy

[Yiheng Wang]

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  wrote:

> Dear Community
>
> I'd like to call a vote on 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
> ,
> 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
>

Podling Livy Report Reminder - January 2020

[jmclean]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, January 01).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/January2020

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [VOTE] Release Livy 0.7.0 based on RC3

[Yiheng Wang]

Check the release files. Looks good.

+1

On Wed, Dec 18, 2019 at 5:25 PM runzhiwang  wrote:

>  
>   +1
>   
>  ** release files*
> I verify the apache-livy-0.7.0-incubating-bin.zip by creating session,
> statement, and everything is ok.
>  I also verify the sha512 and asc file. Both look good.
>
>   ** staged maven artifacts **
>  It's ok.
>   
>
>  ** resolved JIRAs **
>  It's ok. I check all the jiras in the commits.
>   
>
> Thanks
> RunzhiWang
>
>
>
>  -- 原始邮件 --
>   发件人: "Saisai Shao"  发送时间: 2019年12月18日(星期三) 中午1:58
>  收件人: "dev"
>  主题: [VOTE] Release Livy 0.7.0 based on RC3
>
>
>
> This vote is for releasing Livy 0.7.0 based on RC3.
>
> The vote will be open until Friday  Dec 23, 23:59 UTC and
> will pass with a minimum of 3 +1 binding votes and a majority of positive
> votes.
>
> [+1] This release is ready to send to the Incubator PMC for approval
>
> [-1] This release is not ready because...
>
> This vote is held according to Apache Incubator release policy:
> https://incubator.apache.org/policy/incubation.html#releases
>
> The RC is based on tag v0.7.0-incubating-rc3:
>
> https://github.com/apache/incubator-livy/commit/0cc431a7e9236e313f9904ef121cad5df444d4da
>
> The release files can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc3/
>
> The staged maven artifacts can be found here:
> https://repository.apache.org/content/repositories/orgapachelivy-1012
>
> The list of resolved JIRAs in this release can be found here:
> https://issues.apache.org/jira/projects/LIVY/versions/12345179
>
> Thanks
> Saisai

??????[Vote][LIVY-718] Support multi-active high availability in Livy

[runzhiwang]

 
  +1

 

 --  --
  ??: "Yiheng Wang"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
;,
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

??????[VOTE] Release Livy 0.7.0 based on RC3

[runzhiwang]

 
  +1
  
 ** release files*
I verify the apache-livy-0.7.0-incubating-bin.zip by creating session, 
statement, and everything is ok.
 I also verify the sha512 and asc file. Both look good.

  ** staged maven artifacts **
 It's ok.
  

 ** resolved JIRAs **
 It's ok. I check all the jiras in the commits.
  
 
Thanks
RunzhiWang

 

 --  --
  ??: "Saisai Shao"https://incubator.apache.org/policy/incubation.html#releases

The RC is based on tag v0.7.0-incubating-rc3:
https://github.com/apache/incubator-livy/commit/0cc431a7e9236e313f9904ef121cad5df444d4da

The release files can be found here:
https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc3/

The staged maven artifacts can be found here:
https://repository.apache.org/content/repositories/orgapachelivy-1012

The list of resolved JIRAs in this release can be found here:
https://issues.apache.org/jira/projects/LIVY/versions/12345179

Thanks
Saisai