+1 from me. This is the draft PR for upgrading hbase main repo to hbase-thirdparty 4.1.13, which is good, the failed UTs are not related.
https://github.com/apache/hbase/pull/7869 And I also run a 10B ITBLL, although it failed at 9th round's generator job, I did not see any data corruption problems since the failure was memory pressure and too many full GCs. Let's finish this release and then make new hbase releases to resolev the security problems. Thanks. Duo Zhang <[email protected]> 于2026年3月7日周六 17:48写道： > > Please vote on this Apache hbase thirdparty release candidate, > hbase-thirdparty-4.1.13RC1 > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.13 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 4.1.13RC1: > > https://github.com/apache/hbase-thirdparty/tree/4.1.13RC1 > > This tag currently points to git reference > > c4d13cdfbe20cb9cc3b96ce6d567e7f8ac6c2421 > > The release files, including signatures, digests, as well as CHANGES.md > and RELEASENOTES.md included in this RC can be found at: > > https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-4.1.13RC1/ > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1597/ > > Artifacts were signed with the 0x9AD2AE49 key which can be found in: > > https://downloads.apache.org/hbase/KEYS > > To learn more about Apache hbase thirdparty, please see > > http://hbase.apache.org/ > > Thanks, > Your HBase Release Manager
