[jira] [Resolved] (HBASE-27495) Improve HFileLinkCleaner to validate back reference links ahead the next traverse
[ https://issues.apache.org/jira/browse/HBASE-27495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tak-Lon (Stephen) Wu resolved HBASE-27495. -- Hadoop Flags: Reviewed Resolution: Fixed > Improve HFileLinkCleaner to validate back reference links ahead the next > traverse > -- > > Key: HBASE-27495 > URL: https://issues.apache.org/jira/browse/HBASE-27495 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 2.6.0, 3.0.0-alpha-4, 2.5.2 >Reporter: Tak-Lon (Stephen) Wu >Assignee: Tak-Lon (Stephen) Wu >Priority: Major > Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.2 > > > We found a a race in the CleanerChore related to back reference links. When > the HFileLinkCleaner runs for a file it can make 2 decisions depending on the > file types. > - HFiles, The cleaner for HFile deletion only checks if the .links-<> > directory is present with files. > - Back reference links, the cleaner checks if the forward link is still > available in the data directory. > The logic and order how the cleaner checks these 2 files matters. When the > back reference is checked first it can remove both the reference and the > HFile from the archive, however, when it first runs for the HFile then only > the back-reference is removed. In this case, the HFile is only deleted in the > next iteration of the CleanerChore, and it could be very slow if the list of > files are huge in case of using object store. > The goal of this task is to improve traverse of the archived HFile, reusing > the list of found back reference files, and immediately apply the checks for > the Back reference links. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Quickly release 2.5.2 with hadoop3 binaries
After fixing the jackson CVEs, I think it is time to make a new release now. Will put up 2.5.2RC0 next week. Thanks. 张铎(Duo Zhang) 于2022年11月4日周五 23:24写道： > > If there are no big concerns, I will put up a 2.5.2RC0 next week, with > hadoop3 binaries, to see if it could meet our users' requirements. > > Thanks. > > 张铎(Duo Zhang) 于2022年10月31日周一 14:38写道： > > > > emmm, after reading the title, seems the word 'quickly' is a bit confusing > > > > What I mean here is we can start releasing 2.5.2 earlier than usual, > > for verify the hadoop3 binaries, not mean the release process for > > 2.5.2 should be quick. And I even think the release process for 2.5.2 > > should be longer than before, as we want to change the content of the > > release. > > > > Thanks. > > > > 张铎(Duo Zhang) 于2022年10月31日周一 11:58写道： > > > > > > Recently I've been working on HBASE-27359 together with some other > > > folks in the community(Nick, Andrew, Guanghao, etc.). After landing > > > some important improvements, such as HBASE-27434, HBASE-27442 and > > > more, now we are ready to make our release scripts able to publish > > > binaries for hadoop3. > > > > > > https://github.com/apache/hbase/pull/4856 > > > > > > So here, I wonder if we can quickly put up RCs for 2.5.2, with hadoop3 > > > binaries and maven artifacts, so our users in the community can test > > > and use them, report problems. And once we successfully released 2.5.2 > > > with hadoop3 releases, we can merge the PR for HBASE-27359 back, so > > > later the release managers can easily publish binaries and maven > > > artifacts with hadoop3 when making new releases. > > > > > > Thanks.
[jira] [Resolved] (HBASE-27443) Use java11 in the general check of our jenkins job
[ https://issues.apache.org/jira/browse/HBASE-27443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27443. --- Resolution: Fixed No problem now after resolving the sub task. > Use java11 in the general check of our jenkins job > -- > > Key: HBASE-27443 > URL: https://issues.apache.org/jira/browse/HBASE-27443 > Project: HBase > Issue Type: Task > Components: build, jenkins >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.2, 2.4.16 > > > In this way we could also bump the version of error prone plugin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
