You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ratis.apache.org by Yaolong Liu <ly...@163.com> on 2022/07/06 12:43:04 UTC
Re:Ratis-2.3.1 release
Hi all,
Ratis Thirdparty 1.0.1 has been released, and Ratis master branch
upgraded to it. We can proceed with Ratis 2.3.1 release.
I will release based on branch-2. Since there have been many changes recently,
I want to release based on RATIS-1614 and all previous commits.
If there are any that should not appear in 2.3.1, please let me know.
Regards,
Yaolong Liu
At 2022-06-18 17:44:27, "William Song" <sz...@163.com> wrote:
>Hi all,
>
>What’s the community’s plan on release Ratis-2.3.1 version? Apache IoTDB plan to release a major version 0.14.0 by June 30, while current dependency Ratis-2.3.0 have some snapshot bugs that affects the multi-chunk snapshot scenario (see https://issues.apache.org/jira/browse/RATIS-1587 <https://issues.apache.org/jira/browse/RATIS-1587> and https://github.com/apache/ratis/pull/655 <https://github.com/apache/ratis/pull/655> for detail).
>Therefore, we are hoping that the community can release Ratis-2.3.1 version and we are happy to help.
>
>Best Wishes,
>William Song
Re:Re: Re: Re: Ratis-2.3.1 release
Posted by Yaolong Liu <ly...@163.com>.
Hi Tsz-Wo,
Thanks for letting me know that grpc 1.48.1 has been released, also thanks Attila!
I will start the release of ratis-thirdparty 1.0.2.
Regards,
Yaolong Liu
At 2022-08-04 00:55:39, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>Hi Yaolong,
>
>gRPC 1.48.1 has been released and we have merged it to thirdparty (thanks
>Attila!). We may start preparing thirdparty 1.0.2. Thanks.
>
>commit 5fe08eeebc0e6d2530fc1b100f582220670d2bbb (*HEAD -> **master*,
>*origin/master*, *origin/HEAD*)
>
>Author: Doroszlai, Attila <64...@users.noreply.github.com>
>
>Date: Wed Aug 3 18:20:54 2022 +0200
>
>
> RATIS-1632. Upgrade gRPC to 1.48.1 (#36)
>
>Regards,
>Tsz-Wo
>
>On Thu, Jul 28, 2022 at 7:39 AM Yaolong Liu <ly...@163.com> wrote:
>
>> Hi Tsz-Wo,
>>
>>
>> I think using 1.0.2 and 2.4.0 is fine, thanks for the suggestion.
>> Let's wait for grpc 1.48.1 to complete the release before starting the
>> release process for Ratis 2.4.0.
>> Regards,
>> Yaolong Liu
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> At 2022-07-27 23:28:18, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>> >Hi Yaolong,
>> >
>> >For ratis-thirdparty, let's make it 1.0.2 since there are not many
>> changes.
>> >
>> >For ratis, I do suggest calling it 2.4.0 instead of 2.3.1 since there are
>> >quite many changes. What do you think?
>> >
>> >Regards,
>> >Tsz-Wo
>> >
>> >On Wed, Jul 27, 2022 at 7:58 AM Yaolong Liu <ly...@163.com> wrote:
>> >
>> >> Hi Tsz-Wo,
>> >>
>> >>
>> >> Thanks for pointing this out, grpc 1.48.1 seem not be released yet, we
>> can
>> >> wait for it to release and then launch a ratis-thirdparty release.
>> >> The release of Ratis 2.3.1 can be delayed. BTW, should the next version
>> of
>> >> ratis-thirdparty be 1.0.2 or 1.1.0?
>> >>
>> >>
>> >>
>> >>
>> >> Regards,
>> >> Yaolong Liu
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> At 2022-07-27 00:10:53, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>> >> >Hi Yaolong,
>> >> >
>> >> >We probably have to update gRPC in ratis-thirdparty due to the recent
>> gRPC
>> >> >"ByteBuffer memory leak in retry mechanism" issue; see
>> >> >https://github.com/grpc/grpc-java/issues/9340 . According to this
>> >> comment
>> >> >https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690
>> ,
>> >> they
>> >> >will have a fix in 1.48.1 soon.
>> >> >
>> >> >Tsz-Wo
>> >> >
>> >> >
>> >> >On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <ly...@163.com> wrote:
>> >> >
>> >> >> Hi all,
>> >> >>
>> >> >>
>> >> >> Recently ratis has supported listener and fixed multiple bugs, can we
>> >> >> start the release of 2.3.1?
>> >> >> I want to release based on RATIS-1637 and all previous commits.
>> >> >> If there are any that should or should not appear in 2.3.1, please
>> let
>> >> me
>> >> >> know.
>> >> >>
>> >> >>
>> >> >> Regards,
>> >> >> Yaolong Liu
>> >>
>>
Re: Re: Re: Ratis-2.3.1 release
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi Yaolong,
gRPC 1.48.1 has been released and we have merged it to thirdparty (thanks
Attila!). We may start preparing thirdparty 1.0.2. Thanks.
commit 5fe08eeebc0e6d2530fc1b100f582220670d2bbb (*HEAD -> **master*,
*origin/master*, *origin/HEAD*)
Author: Doroszlai, Attila <64...@users.noreply.github.com>
Date: Wed Aug 3 18:20:54 2022 +0200
RATIS-1632. Upgrade gRPC to 1.48.1 (#36)
Regards,
Tsz-Wo
On Thu, Jul 28, 2022 at 7:39 AM Yaolong Liu <ly...@163.com> wrote:
> Hi Tsz-Wo,
>
>
> I think using 1.0.2 and 2.4.0 is fine, thanks for the suggestion.
> Let's wait for grpc 1.48.1 to complete the release before starting the
> release process for Ratis 2.4.0.
> Regards,
> Yaolong Liu
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2022-07-27 23:28:18, "Tsz Wo Sze" <sz...@gmail.com> wrote:
> >Hi Yaolong,
> >
> >For ratis-thirdparty, let's make it 1.0.2 since there are not many
> changes.
> >
> >For ratis, I do suggest calling it 2.4.0 instead of 2.3.1 since there are
> >quite many changes. What do you think?
> >
> >Regards,
> >Tsz-Wo
> >
> >On Wed, Jul 27, 2022 at 7:58 AM Yaolong Liu <ly...@163.com> wrote:
> >
> >> Hi Tsz-Wo,
> >>
> >>
> >> Thanks for pointing this out, grpc 1.48.1 seem not be released yet, we
> can
> >> wait for it to release and then launch a ratis-thirdparty release.
> >> The release of Ratis 2.3.1 can be delayed. BTW, should the next version
> of
> >> ratis-thirdparty be 1.0.2 or 1.1.0?
> >>
> >>
> >>
> >>
> >> Regards,
> >> Yaolong Liu
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> At 2022-07-27 00:10:53, "Tsz Wo Sze" <sz...@gmail.com> wrote:
> >> >Hi Yaolong,
> >> >
> >> >We probably have to update gRPC in ratis-thirdparty due to the recent
> gRPC
> >> >"ByteBuffer memory leak in retry mechanism" issue; see
> >> >https://github.com/grpc/grpc-java/issues/9340 . According to this
> >> comment
> >> >https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690
> ,
> >> they
> >> >will have a fix in 1.48.1 soon.
> >> >
> >> >Tsz-Wo
> >> >
> >> >
> >> >On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <ly...@163.com> wrote:
> >> >
> >> >> Hi all,
> >> >>
> >> >>
> >> >> Recently ratis has supported listener and fixed multiple bugs, can we
> >> >> start the release of 2.3.1?
> >> >> I want to release based on RATIS-1637 and all previous commits.
> >> >> If there are any that should or should not appear in 2.3.1, please
> let
> >> me
> >> >> know.
> >> >>
> >> >>
> >> >> Regards,
> >> >> Yaolong Liu
> >>
>
Re:Re: Re: Ratis-2.3.1 release
Posted by Yaolong Liu <ly...@163.com>.
Hi Tsz-Wo,
I think using 1.0.2 and 2.4.0 is fine, thanks for the suggestion.
Let's wait for grpc 1.48.1 to complete the release before starting the release process for Ratis 2.4.0.
Regards,
Yaolong Liu
At 2022-07-27 23:28:18, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>Hi Yaolong,
>
>For ratis-thirdparty, let's make it 1.0.2 since there are not many changes.
>
>For ratis, I do suggest calling it 2.4.0 instead of 2.3.1 since there are
>quite many changes. What do you think?
>
>Regards,
>Tsz-Wo
>
>On Wed, Jul 27, 2022 at 7:58 AM Yaolong Liu <ly...@163.com> wrote:
>
>> Hi Tsz-Wo,
>>
>>
>> Thanks for pointing this out, grpc 1.48.1 seem not be released yet, we can
>> wait for it to release and then launch a ratis-thirdparty release.
>> The release of Ratis 2.3.1 can be delayed. BTW, should the next version of
>> ratis-thirdparty be 1.0.2 or 1.1.0?
>>
>>
>>
>>
>> Regards,
>> Yaolong Liu
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> At 2022-07-27 00:10:53, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>> >Hi Yaolong,
>> >
>> >We probably have to update gRPC in ratis-thirdparty due to the recent gRPC
>> >"ByteBuffer memory leak in retry mechanism" issue; see
>> >https://github.com/grpc/grpc-java/issues/9340 . According to this
>> comment
>> >https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690 ,
>> they
>> >will have a fix in 1.48.1 soon.
>> >
>> >Tsz-Wo
>> >
>> >
>> >On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <ly...@163.com> wrote:
>> >
>> >> Hi all,
>> >>
>> >>
>> >> Recently ratis has supported listener and fixed multiple bugs, can we
>> >> start the release of 2.3.1?
>> >> I want to release based on RATIS-1637 and all previous commits.
>> >> If there are any that should or should not appear in 2.3.1, please let
>> me
>> >> know.
>> >>
>> >>
>> >> Regards,
>> >> Yaolong Liu
>>
Re: Re: Ratis-2.3.1 release
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi Yaolong,
For ratis-thirdparty, let's make it 1.0.2 since there are not many changes.
For ratis, I do suggest calling it 2.4.0 instead of 2.3.1 since there are
quite many changes. What do you think?
Regards,
Tsz-Wo
On Wed, Jul 27, 2022 at 7:58 AM Yaolong Liu <ly...@163.com> wrote:
> Hi Tsz-Wo,
>
>
> Thanks for pointing this out, grpc 1.48.1 seem not be released yet, we can
> wait for it to release and then launch a ratis-thirdparty release.
> The release of Ratis 2.3.1 can be delayed. BTW, should the next version of
> ratis-thirdparty be 1.0.2 or 1.1.0?
>
>
>
>
> Regards,
> Yaolong Liu
>
>
>
>
>
>
>
>
>
>
>
> At 2022-07-27 00:10:53, "Tsz Wo Sze" <sz...@gmail.com> wrote:
> >Hi Yaolong,
> >
> >We probably have to update gRPC in ratis-thirdparty due to the recent gRPC
> >"ByteBuffer memory leak in retry mechanism" issue; see
> >https://github.com/grpc/grpc-java/issues/9340 . According to this
> comment
> >https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690 ,
> they
> >will have a fix in 1.48.1 soon.
> >
> >Tsz-Wo
> >
> >
> >On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <ly...@163.com> wrote:
> >
> >> Hi all,
> >>
> >>
> >> Recently ratis has supported listener and fixed multiple bugs, can we
> >> start the release of 2.3.1?
> >> I want to release based on RATIS-1637 and all previous commits.
> >> If there are any that should or should not appear in 2.3.1, please let
> me
> >> know.
> >>
> >>
> >> Regards,
> >> Yaolong Liu
>
Re:Re: Ratis-2.3.1 release
Posted by Yaolong Liu <ly...@163.com>.
Hi Tsz-Wo,
Thanks for pointing this out, grpc 1.48.1 seem not be released yet, we can wait for it to release and then launch a ratis-thirdparty release.
The release of Ratis 2.3.1 can be delayed. BTW, should the next version of ratis-thirdparty be 1.0.2 or 1.1.0?
Regards,
Yaolong Liu
At 2022-07-27 00:10:53, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>Hi Yaolong,
>
>We probably have to update gRPC in ratis-thirdparty due to the recent gRPC
>"ByteBuffer memory leak in retry mechanism" issue; see
>https://github.com/grpc/grpc-java/issues/9340 . According to this comment
>https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690 , they
>will have a fix in 1.48.1 soon.
>
>Tsz-Wo
>
>
>On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <ly...@163.com> wrote:
>
>> Hi all,
>>
>>
>> Recently ratis has supported listener and fixed multiple bugs, can we
>> start the release of 2.3.1?
>> I want to release based on RATIS-1637 and all previous commits.
>> If there are any that should or should not appear in 2.3.1, please let me
>> know.
>>
>>
>> Regards,
>> Yaolong Liu
Re: Ratis-2.3.1 release
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi Yaolong,
We probably have to update gRPC in ratis-thirdparty due to the recent gRPC
"ByteBuffer memory leak in retry mechanism" issue; see
https://github.com/grpc/grpc-java/issues/9340 . According to this comment
https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690 , they
will have a fix in 1.48.1 soon.
Tsz-Wo
On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <ly...@163.com> wrote:
> Hi all,
>
>
> Recently ratis has supported listener and fixed multiple bugs, can we
> start the release of 2.3.1?
> I want to release based on RATIS-1637 and all previous commits.
> If there are any that should or should not appear in 2.3.1, please let me
> know.
>
>
> Regards,
> Yaolong Liu
Ratis-2.3.1 release
Posted by Yaolong Liu <ly...@163.com>.
Hi all,
Recently ratis has supported listener and fixed multiple bugs, can we start the release of 2.3.1?
I want to release based on RATIS-1637 and all previous commits.
If there are any that should or should not appear in 2.3.1, please let me know.
Regards,
Yaolong Liu
Re:Re: Ratis-2.3.1 release
Posted by Yaolong Liu <ly...@163.com>.
Hi Tsz-Wo,
I'll finish RATIS-1612 in the near future,
it's not that urgent right now, so I think we can hold off on finishing the 2.3.1 release.
Regards.
Yaolong Liu
At 2022-07-07 03:27:40, "Tsz Wo Sze" <sz...@gmail.com> wrote:
>Also, if we are not in a hurry, we should also complete
>https://issues.apache.org/jira/browse/RATIS-1612 and include it in 2.3.1.
>Otherwise, the Listener feature is hard to use.
>
>Tsz-Wo
>
>
>On Wed, Jul 6, 2022 at 10:30 AM Tsz Wo Sze <sz...@gmail.com> wrote:
>
>> Hi Yaolong,
>>
>> Just found that we have not yet removed the dropwizard dependencies. We
>> should remove all the dropwizard dependencies and change all the imports to
>> org.apache.ratis.thirdparty.com.codahale.metrics.*; see
>> https://issues.apache.org/jira/browse/RATIS-1601
>>
>> Tsz-Wo
>>
>>
>> On Wed, Jul 6, 2022 at 5:43 AM Yaolong Liu <ly...@163.com> wrote:
>>
>>> Hi all,
>>>
>>> Ratis Thirdparty 1.0.1 has been released, and Ratis master branch
>>> upgraded to it. We can proceed with Ratis 2.3.1 release.
>>>
>>> I will release based on branch-2. Since there have been many changes
>>> recently,
>>> I want to release based on RATIS-1614 and all previous commits.
>>> If there are any that should not appear in 2.3.1, please let me know.
>>>
>>>
>>> Regards,
>>> Yaolong Liu
>>>
>>>
>>>
>>>
>>>
>>> At 2022-06-18 17:44:27, "William Song" <sz...@163.com> wrote:
>>> >Hi all,
>>> >
>>> >What’s the community’s plan on release Ratis-2.3.1 version? Apache IoTDB
>>> plan to release a major version 0.14.0 by June 30, while current dependency
>>> Ratis-2.3.0 have some snapshot bugs that affects the multi-chunk snapshot
>>> scenario (see https://issues.apache.org/jira/browse/RATIS-1587 <
>>> https://issues.apache.org/jira/browse/RATIS-1587> and
>>> https://github.com/apache/ratis/pull/655 <
>>> https://github.com/apache/ratis/pull/655> for detail).
>>> >Therefore, we are hoping that the community can release Ratis-2.3.1
>>> version and we are happy to help.
>>> >
>>> >Best Wishes,
>>> >William Song
>>>
>>
Re: Ratis-2.3.1 release
Posted by Tsz Wo Sze <sz...@gmail.com>.
Also, if we are not in a hurry, we should also complete
https://issues.apache.org/jira/browse/RATIS-1612 and include it in 2.3.1.
Otherwise, the Listener feature is hard to use.
Tsz-Wo
On Wed, Jul 6, 2022 at 10:30 AM Tsz Wo Sze <sz...@gmail.com> wrote:
> Hi Yaolong,
>
> Just found that we have not yet removed the dropwizard dependencies. We
> should remove all the dropwizard dependencies and change all the imports to
> org.apache.ratis.thirdparty.com.codahale.metrics.*; see
> https://issues.apache.org/jira/browse/RATIS-1601
>
> Tsz-Wo
>
>
> On Wed, Jul 6, 2022 at 5:43 AM Yaolong Liu <ly...@163.com> wrote:
>
>> Hi all,
>>
>> Ratis Thirdparty 1.0.1 has been released, and Ratis master branch
>> upgraded to it. We can proceed with Ratis 2.3.1 release.
>>
>> I will release based on branch-2. Since there have been many changes
>> recently,
>> I want to release based on RATIS-1614 and all previous commits.
>> If there are any that should not appear in 2.3.1, please let me know.
>>
>>
>> Regards,
>> Yaolong Liu
>>
>>
>>
>>
>>
>> At 2022-06-18 17:44:27, "William Song" <sz...@163.com> wrote:
>> >Hi all,
>> >
>> >What’s the community’s plan on release Ratis-2.3.1 version? Apache IoTDB
>> plan to release a major version 0.14.0 by June 30, while current dependency
>> Ratis-2.3.0 have some snapshot bugs that affects the multi-chunk snapshot
>> scenario (see https://issues.apache.org/jira/browse/RATIS-1587 <
>> https://issues.apache.org/jira/browse/RATIS-1587> and
>> https://github.com/apache/ratis/pull/655 <
>> https://github.com/apache/ratis/pull/655> for detail).
>> >Therefore, we are hoping that the community can release Ratis-2.3.1
>> version and we are happy to help.
>> >
>> >Best Wishes,
>> >William Song
>>
>
Re: Ratis-2.3.1 release
Posted by Tsz Wo Sze <sz...@gmail.com>.
Hi Yaolong,
Just found that we have not yet removed the dropwizard dependencies. We
should remove all the dropwizard dependencies and change all the imports to
org.apache.ratis.thirdparty.com.codahale.metrics.*; see
https://issues.apache.org/jira/browse/RATIS-1601
Tsz-Wo
On Wed, Jul 6, 2022 at 5:43 AM Yaolong Liu <ly...@163.com> wrote:
> Hi all,
>
> Ratis Thirdparty 1.0.1 has been released, and Ratis master branch
> upgraded to it. We can proceed with Ratis 2.3.1 release.
>
> I will release based on branch-2. Since there have been many changes
> recently,
> I want to release based on RATIS-1614 and all previous commits.
> If there are any that should not appear in 2.3.1, please let me know.
>
>
> Regards,
> Yaolong Liu
>
>
>
>
>
> At 2022-06-18 17:44:27, "William Song" <sz...@163.com> wrote:
> >Hi all,
> >
> >What’s the community’s plan on release Ratis-2.3.1 version? Apache IoTDB
> plan to release a major version 0.14.0 by June 30, while current dependency
> Ratis-2.3.0 have some snapshot bugs that affects the multi-chunk snapshot
> scenario (see https://issues.apache.org/jira/browse/RATIS-1587 <
> https://issues.apache.org/jira/browse/RATIS-1587> and
> https://github.com/apache/ratis/pull/655 <
> https://github.com/apache/ratis/pull/655> for detail).
> >Therefore, we are hoping that the community can release Ratis-2.3.1
> version and we are happy to help.
> >
> >Best Wishes,
> >William Song
>