You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ratis.apache.org by "Elek, Marton" <el...@apache.org> on 2021/02/02 10:16:16 UTC
Ratis 2.0 release
Yesterday we had a long conversation about Ratis release during the
Ozone community call [1]:
1. We think that the easiest way to release is Ozone to release Ratis
master as Ratis 2.0 (full branch, without cherry-picking)
2. All the new features can be turned off by default (like PRE_VOTE
and leader lease). Either by default on Ratis, or just by the Ozone.
(follow HDDS-4774)
3. Compatibility will be tested by acceptance tests (thx to Attila we
will have a test to test current Ozone with older clients).
From this point of view, Ozone needs 2.0 release from master.
runzhiwang: you are volunteered to be an RM for 1.1. Do you need a
stable 1.1 release, or you would do it for Ozone.
If it's for Ozone, can we do 2.0 instead?
(I am happy to help in any release which moves us closer to the Ozone
release).
Thanks,
Marton
[1]: in the first 30 mins
https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ
Passcode: $PS1wQ.N
Re: Ratis 2.0 release
Posted by "Elek, Marton" <el...@apache.org>.
+ 1 to publish stable, "snapshot"-like releases from the Ratis
frequently For example a monthly patch release from the latest stable
branch.
Nanda had similar suggestion during the community meeting (Ozone should
depend on properly released patch releases from Ratis instead of snapshots).
I just shared the archive of the community call on the Ozone dev list
which includes the discussion.
One additional argument was that Ratis 1.1 branch is not something which
is ready to use, but it requires more work (triage / cherry-pick) which
has additional risk compared to using the already-tested Ratis master
(with disabled new features.)
Marton
On 2/2/21 7:45 PM, Attila Doroszlai wrote:
>> It is odd that 2.0 is expected to be more stable than 1.1 when 2.0 should
>> be a superset of 1.1.
>
> My understanding is that current Ratis master (to become 2.0) is more
> extensively tested in "production" via Ozone. Ratis 1.1 may be more
> stable feature-wise, but there is an uncertainty factor because fixes
> still need to be cherry-picked and integration tested.
>
> In the future I think it would be better to establish a maintenance
> branch from which snapshots could be released for Ozone. This would
> let Ozone to take critical fixes in a timely manner without becoming
> dependent on the in-development version including new API etc.
>
> -Attila
>
Re: Ratis 2.0 release
Posted by Attila Doroszlai <ad...@apache.org>.
> It is odd that 2.0 is expected to be more stable than 1.1 when 2.0 should
> be a superset of 1.1.
My understanding is that current Ratis master (to become 2.0) is more
extensively tested in "production" via Ozone. Ratis 1.1 may be more
stable feature-wise, but there is an uncertainty factor because fixes
still need to be cherry-picked and integration tested.
In the future I think it would be better to establish a maintenance
branch from which snapshots could be released for Ozone. This would
let Ozone to take critical fixes in a timely manner without becoming
dependent on the in-development version including new API etc.
-Attila
Re: Ratis 2.0 release
Posted by Rui Wang <am...@apache.org>.
I didn't join the community call thus may not know enough context.
> It is odd that 2.0 is expected to be more stable than 1.1 when 2.0 should
be a superset of 1.1.
so I have the same question as Arpit.
-Rui
On Tue, Feb 2, 2021 at 7:36 AM Arpit Agarwal <aa...@cloudera.com.invalid>
wrote:
> Which version of Ratis will Ozone 1.1 use?
>
> It is odd that 2.0 is expected to be more stable than 1.1 when 2.0 should
> be a superset of 1.1.
>
> Thanks,
> Arpit
>
> > On Feb 2, 2021, at 3:35 AM, runzhiwang <ru...@gmail.com> wrote:
> >
> > I agree, I will release ratis 2.0.0 first.
> >
> > Thanks,
> > runzhiwang
> >
> > Shashikant Banerjee <sb...@cloudera.com.invalid> 于2021年2月2日周二
> 下午7:33写道：
> >
> >> Let's get ratis 2.0.0 out first. Ratis 1.1 may require some more testing
> >> for stability.
> >>
> >> Thanks @runzhiwang(王杰) <ru...@tencent.com> for volunteering for
> the
> >> same.
> >>
> >> Thanks
> >> Shashi
> >>
> >> On Tue, Feb 2, 2021 at 4:44 PM runzhiwang <ru...@gmail.com>
> wrote:
> >>
> >>> Hi Marton,
> >>>
> >>> Thanks the suggestions, I'm okay to release ratis 2.0.0 first. After
> >>> release 2.0, I will also release ratis 1.1, so that other application,
> >> such
> >>> as Alluxio, can use ratis 1.1.
> >>>
> >>> Thanks,
> >>> runzhiwang
> >>>
> >>> Elek, Marton <el...@apache.org> 于2021年2月2日周二 下午6:16写道：
> >>>
> >>>>
> >>>> Yesterday we had a long conversation about Ratis release during the
> >>>> Ozone community call [1]:
> >>>>
> >>>> 1. We think that the easiest way to release is Ozone to release Ratis
> >>>> master as Ratis 2.0 (full branch, without cherry-picking)
> >>>>
> >>>> 2. All the new features can be turned off by default (like PRE_VOTE
> >>>> and leader lease). Either by default on Ratis, or just by the Ozone.
> >>>> (follow HDDS-4774)
> >>>>
> >>>> 3. Compatibility will be tested by acceptance tests (thx to Attila we
> >>>> will have a test to test current Ozone with older clients).
> >>>>
> >>>>
> >>>> From this point of view, Ozone needs 2.0 release from master.
> >>>>
> >>>> runzhiwang: you are volunteered to be an RM for 1.1. Do you need a
> >>>> stable 1.1 release, or you would do it for Ozone.
> >>>>
> >>>> If it's for Ozone, can we do 2.0 instead?
> >>>>
> >>>> (I am happy to help in any release which moves us closer to the Ozone
> >>>> release).
> >>>>
> >>>> Thanks,
> >>>> Marton
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> [1]: in the first 30 mins
> >>>>
> >>>>
> >>>>
> >>>
> >>
> https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ
> >>>>
> >>>> Passcode: $PS1wQ.N
> >>>>
> >>>
> >>
>
>
Re: Ratis 2.0 release
Posted by Arpit Agarwal <aa...@cloudera.com.INVALID>.
Which version of Ratis will Ozone 1.1 use?
It is odd that 2.0 is expected to be more stable than 1.1 when 2.0 should be a superset of 1.1.
Thanks,
Arpit
> On Feb 2, 2021, at 3:35 AM, runzhiwang <ru...@gmail.com> wrote:
>
> I agree, I will release ratis 2.0.0 first.
>
> Thanks,
> runzhiwang
>
> Shashikant Banerjee <sb...@cloudera.com.invalid> 于2021年2月2日周二 下午7:33写道：
>
>> Let's get ratis 2.0.0 out first. Ratis 1.1 may require some more testing
>> for stability.
>>
>> Thanks @runzhiwang(王杰) <ru...@tencent.com> for volunteering for the
>> same.
>>
>> Thanks
>> Shashi
>>
>> On Tue, Feb 2, 2021 at 4:44 PM runzhiwang <ru...@gmail.com> wrote:
>>
>>> Hi Marton,
>>>
>>> Thanks the suggestions, I'm okay to release ratis 2.0.0 first. After
>>> release 2.0, I will also release ratis 1.1, so that other application,
>> such
>>> as Alluxio, can use ratis 1.1.
>>>
>>> Thanks,
>>> runzhiwang
>>>
>>> Elek, Marton <el...@apache.org> 于2021年2月2日周二 下午6:16写道：
>>>
>>>>
>>>> Yesterday we had a long conversation about Ratis release during the
>>>> Ozone community call [1]:
>>>>
>>>> 1. We think that the easiest way to release is Ozone to release Ratis
>>>> master as Ratis 2.0 (full branch, without cherry-picking)
>>>>
>>>> 2. All the new features can be turned off by default (like PRE_VOTE
>>>> and leader lease). Either by default on Ratis, or just by the Ozone.
>>>> (follow HDDS-4774)
>>>>
>>>> 3. Compatibility will be tested by acceptance tests (thx to Attila we
>>>> will have a test to test current Ozone with older clients).
>>>>
>>>>
>>>> From this point of view, Ozone needs 2.0 release from master.
>>>>
>>>> runzhiwang: you are volunteered to be an RM for 1.1. Do you need a
>>>> stable 1.1 release, or you would do it for Ozone.
>>>>
>>>> If it's for Ozone, can we do 2.0 instead?
>>>>
>>>> (I am happy to help in any release which moves us closer to the Ozone
>>>> release).
>>>>
>>>> Thanks,
>>>> Marton
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> [1]: in the first 30 mins
>>>>
>>>>
>>>>
>>>
>> https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ
>>>>
>>>> Passcode: $PS1wQ.N
>>>>
>>>
>>
Re: Ratis 2.0 release
Posted by runzhiwang <ru...@gmail.com>.
I agree, I will release ratis 2.0.0 first.
Thanks,
runzhiwang
Shashikant Banerjee <sb...@cloudera.com.invalid> 于2021年2月2日周二 下午7:33写道：
> Let's get ratis 2.0.0 out first. Ratis 1.1 may require some more testing
> for stability.
>
> Thanks @runzhiwang(王杰) <ru...@tencent.com> for volunteering for the
> same.
>
> Thanks
> Shashi
>
> On Tue, Feb 2, 2021 at 4:44 PM runzhiwang <ru...@gmail.com> wrote:
>
> > Hi Marton,
> >
> > Thanks the suggestions, I'm okay to release ratis 2.0.0 first. After
> > release 2.0, I will also release ratis 1.1, so that other application,
> such
> > as Alluxio, can use ratis 1.1.
> >
> > Thanks,
> > runzhiwang
> >
> > Elek, Marton <el...@apache.org> 于2021年2月2日周二 下午6:16写道：
> >
> > >
> > > Yesterday we had a long conversation about Ratis release during the
> > > Ozone community call [1]:
> > >
> > > 1. We think that the easiest way to release is Ozone to release Ratis
> > > master as Ratis 2.0 (full branch, without cherry-picking)
> > >
> > > 2. All the new features can be turned off by default (like PRE_VOTE
> > > and leader lease). Either by default on Ratis, or just by the Ozone.
> > > (follow HDDS-4774)
> > >
> > > 3. Compatibility will be tested by acceptance tests (thx to Attila we
> > > will have a test to test current Ozone with older clients).
> > >
> > >
> > > From this point of view, Ozone needs 2.0 release from master.
> > >
> > > runzhiwang: you are volunteered to be an RM for 1.1. Do you need a
> > > stable 1.1 release, or you would do it for Ozone.
> > >
> > > If it's for Ozone, can we do 2.0 instead?
> > >
> > > (I am happy to help in any release which moves us closer to the Ozone
> > > release).
> > >
> > > Thanks,
> > > Marton
> > >
> > >
> > >
> > >
> > >
> > >
> > > [1]: in the first 30 mins
> > >
> > >
> > >
> >
> https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ
> > >
> > > Passcode: $PS1wQ.N
> > >
> >
>
Re: Ratis 2.0 release
Posted by Shashikant Banerjee <sb...@cloudera.com.INVALID>.
Let's get ratis 2.0.0 out first. Ratis 1.1 may require some more testing
for stability.
Thanks @runzhiwang(王杰) <ru...@tencent.com> for volunteering for the
same.
Thanks
Shashi
On Tue, Feb 2, 2021 at 4:44 PM runzhiwang <ru...@gmail.com> wrote:
> Hi Marton,
>
> Thanks the suggestions, I'm okay to release ratis 2.0.0 first. After
> release 2.0, I will also release ratis 1.1, so that other application, such
> as Alluxio, can use ratis 1.1.
>
> Thanks,
> runzhiwang
>
> Elek, Marton <el...@apache.org> 于2021年2月2日周二 下午6:16写道：
>
> >
> > Yesterday we had a long conversation about Ratis release during the
> > Ozone community call [1]:
> >
> > 1. We think that the easiest way to release is Ozone to release Ratis
> > master as Ratis 2.0 (full branch, without cherry-picking)
> >
> > 2. All the new features can be turned off by default (like PRE_VOTE
> > and leader lease). Either by default on Ratis, or just by the Ozone.
> > (follow HDDS-4774)
> >
> > 3. Compatibility will be tested by acceptance tests (thx to Attila we
> > will have a test to test current Ozone with older clients).
> >
> >
> > From this point of view, Ozone needs 2.0 release from master.
> >
> > runzhiwang: you are volunteered to be an RM for 1.1. Do you need a
> > stable 1.1 release, or you would do it for Ozone.
> >
> > If it's for Ozone, can we do 2.0 instead?
> >
> > (I am happy to help in any release which moves us closer to the Ozone
> > release).
> >
> > Thanks,
> > Marton
> >
> >
> >
> >
> >
> >
> > [1]: in the first 30 mins
> >
> >
> >
> https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ
> >
> > Passcode: $PS1wQ.N
> >
>
Re: Ratis 2.0 release
Posted by runzhiwang <ru...@gmail.com>.
Hi Marton,
Thanks the suggestions, I'm okay to release ratis 2.0.0 first. After
release 2.0, I will also release ratis 1.1, so that other application, such
as Alluxio, can use ratis 1.1.
Thanks,
runzhiwang
Elek, Marton <el...@apache.org> 于2021年2月2日周二 下午6:16写道：
>
> Yesterday we had a long conversation about Ratis release during the
> Ozone community call [1]:
>
> 1. We think that the easiest way to release is Ozone to release Ratis
> master as Ratis 2.0 (full branch, without cherry-picking)
>
> 2. All the new features can be turned off by default (like PRE_VOTE
> and leader lease). Either by default on Ratis, or just by the Ozone.
> (follow HDDS-4774)
>
> 3. Compatibility will be tested by acceptance tests (thx to Attila we
> will have a test to test current Ozone with older clients).
>
>
> From this point of view, Ozone needs 2.0 release from master.
>
> runzhiwang: you are volunteered to be an RM for 1.1. Do you need a
> stable 1.1 release, or you would do it for Ozone.
>
> If it's for Ozone, can we do 2.0 instead?
>
> (I am happy to help in any release which moves us closer to the Ozone
> release).
>
> Thanks,
> Marton
>
>
>
>
>
>
> [1]: in the first 30 mins
>
>
> https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ
>
> Passcode: $PS1wQ.N
>