Thanks for the feedback Charles. I have rebased the HBASE-28596 PR to
branch-2.6, we should be able to merge it today.

Em qua., 25 de jun. de 2025 às 22:12, Charles Connell
<cconn...@hubspot.com.invalid> escreveu:

> I vote -1 because I feel that HBASE-28596 should be included in 2.6.3.
> There is an open PR to accomplish this:
> https://github.com/apache/hbase/pull/6508. This will fix a performance
> regression that was introduced in 2.6.0 by HBASE-27474. The regression
> is described in HBASE-29012, but to summarize: logic was added so that
> we don't cache blocks that exist within a reference or a link. This is
> a significant issue. At Hubspot we had to apply the patch from the PR
> to our fork in order to have acceptable performance.
>
> Charles
>
> On Sat, Jun 21, 2025 at 9:48 PM Duo Zhang <zhang...@apache.org> wrote:
> >
> > Please vote on this Apache hbase release candidate,
> > hbase-2.6.3RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.6.3
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.6.3RC0:
> >
> > https://github.com/apache/hbase/tree/2.6.3RC0
> >
> > This tag currently points to git reference
> >
> > bd91bafe4236c0a4dbba38a4cc735dfe9db67cd6
> >
> > 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/2.6.3RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1578/
> >
> > Maven artifacts for hadoop3 are available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1579/
> >
> > Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> >
> > https://downloads.apache.org/hbase/KEYS
> >
> > To learn more about Apache hbase, please see
> >
> > http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
>
>

Reply via email to