Are we ready to make the 2.6.1 release now? Are there any remaining issues that need to be addressed?
Thanks. Dieter De Paepe <diete...@ngdata.com.invalid> 于2024年7月2日周二 22:53写道： > > I found 2 more possible causes for data loss when using multiple backup > roots. These should also be included in the 2.6.1 in my opinion. > Unfortunately, I only had time to fix one of them: > > > * HBASE-28705 (PR available) > > * HBASE-28706 > > Regards, > Dieter > ________________________________ > From: Dieter De Paepe <diete...@ngdata.com.INVALID> > Sent: 10 June 2024 15:29 > To: dev@hbase.apache.org <dev@hbase.apache.org> > Subject: Re: [DISCUSS] Blockers for 2.6.1 > > Hi Bryan, > > I suggest to add HBASE-28389, and possibly HBASE-28103 to the list as well, > as they both cause some kind of broken functionality. > > Regards, > Dieter > ________________________________ > From: Bryan Beaudreault <bbeaudrea...@apache.org> > Sent: 05 June 2024 21:34 > To: HBase Dev List <dev@hbase.apache.org> > Subject: [DISCUSS] Blockers for 2.6.1 > > Hey all, > > It's been 2 weeks since 2.6.0 was released. As discussed in the vote > thread, there were a few outstanding backup-related issues. I believe we've > made some progress on some of those. > > I'd like to start compiling a list of important backup-related fixes to > target for the 2.6.1 release so that we can track progress. Can those of > you who are involved (Ray Mattingly, Nick Dimiduck, Dieter De Paepe & team, > and any others) please list any important jiras here? > > With a list of jiras in hand, we can check to make sure blockers & > fixVersions are set and use that to track what we need to drill down before > releasing. > > Here's what I know of so far, let me know if I'm missing anything: > > Not yet started: > - HBASE-28084: incremental backups should be forbidden after deleting > backups > - HBASE-28602: Incremental backup fails when WALs move > - HBASE-28462: (similar to ^, but in a different part of the code) > - HBASE-28538: BackupHFileCleaner is very expensive > > Patch available: > - HBASE-28539: backup merging does not work when using cloud storage as > filesystem > - HBASE-28562: another possible failure cause for incremental backups + > possibly cause of overly big backup metadata > > Resolved: > - HBASE-28502: backed up tables are not listed correctly in backup > metadata, which causes unreliable backup validation > - HBASE-28568: the set of tables included in incremental backups might be > too big
