Netty 4.1.107.Final has been released. I pushed https://github.com/apache/hbase-thirdparty/pull/108 to upgrade. Once that is merged, I will look into how to do an hbase-thirdparty release (unless anyone else has bandwidth?)
I also finally got ITBLL/ChaosMonkey working in my company's environment. Am running ITBLL on 2.6.0-SNAPSHOT now. On Thu, Jan 25, 2024 at 9:34 PM Bryan Beaudreault <bbeaudrea...@apache.org> wrote: > Also we need a release of hbase-thirdparty first anyway for some CVEs, so > just trying to avoid having to make another release right afterward for > this other fix. > > On Thu, Jan 25, 2024 at 9:33 PM Bryan Beaudreault <bbeaudrea...@apache.org> > wrote: > >> No it’s not critical. It’s a small thing related to certificate parsing ( >> https://github.com/netty/netty/issues/13796). We need it for our usage >> of https://github.com/apache/hbase/pull/5644. This wouldn't need to >> block things, but I think the timing is good, and it also would be nice to >> ship the TLS features without any known issues. If there were a more urgent >> need, we could definitely go without. >> >> On Thu, Jan 25, 2024 at 8:11 PM 张铎(Duo Zhang) <palomino...@gmail.com> >> wrote: >> >>> Sounds good. >>> >>> And I think in this way we could also expect the rpc connection >>> registry related issues to be fixed before tagging 2.6.0RC0. >>> >>> BTW, what is the TLS fix in netty? Is it critical? >>> >>> Thanks. >>> >>> Bryan Beaudreault <bbeaudrea...@apache.org> 于2024年1月25日周四 22:08写道： >>> > >>> > We are almost ready. In my spare time I am still doing some testing on >>> a >>> > larger cluster. My initial tests uncovered some minor issues, which >>> have >>> > been fixed. If there are no other issues, we can move forward. >>> > >>> > For now I would like to wait for netty release 4.1.107.Final, which >>> Normal >>> > tells me should be in the next 2-3 weeks. The reason is that there is >>> a fix >>> > for TLS, and 2.6.0 is our first release with TLS. >>> > >>> > So my checklist at this point is: >>> > 1. Continue testing on a larger cluster >>> > 2. Resolve fixVersions discrepancies (there are only a few) >>> > 3. Update hbase-thirdparty to 4.1.107.Final and create a release of >>> that. >>> > 4. Update hbase to use that new release of hbase-thirdparty >>> > 5. Create 2.6.0RC0 >>> > >>> > Let me know if anyone has issues with this timeline. We don't >>> absolutely >>> > _have_ to wait for netty, but it would be nice. >>> >>
