[RESULT][VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
Oh, forgot to change the title... 张铎(Duo Zhang) 于2022年6月22日周三 10:17写道： > With 6 binding +1s and no -1, the vote passes. > > Let me finish the release. > > Thanks all for voting and helping! > > 张铎(Duo Zhang) 于2022年6月22日周三 10:16写道： > >> Here is my own +1. >> >> Yu Li 于2022年6月21日周二 23:24写道： >> >>> Thanks for the quick reply Duo, makes sense to me. >>> >>> And thanks for driving this release. >>> >>> Best Regards, >>> Yu >>> >>> >>> On Tue, 21 Jun 2022 at 23:17, 张铎(Duo Zhang) >>> wrote: >>> >>> > Thanks Yu. >>> > >>> > We do not write release note for HBASE-26893(my fault) so the generate >>> > RELEASENOTES.md does not have the release note for this change. >>> > >>> > I thought the title just tells everything so I did not add a release >>> note >>> > for it... >>> > >>> > Anyway, not a blocker this time. In the future will rememer to always >>> add a >>> > release note for an issue when we bump a dependency. >>> > >>> > Thanks. >>> > >>> > Yu Li 于2022年6月21日周二 23:02写道： >>> > >>> > > +1 (binding) >>> > > >>> > > Checked the diff between 4.1.0 and 4.1.1-rc0: *OK* ( >>> > > >>> https://github.com/apache/hbase-thirdparty/compare/rel/4.1.0...4.1.1RC0) >>> > > Checked release note and changes: *Minor Update Required* >>> > > - It seems we should also include HBASE-26893 (jackson updated to >>> 2.13.3) >>> > > into release note (RELEASENOTES.md) >>> > > Checked sums and signatures: *OK* >>> > > Maven clean install from source (8u121): *OK* >>> > > Checked the jars in the staging repo: *OK* >>> > > >>> > > Best Regards, >>> > > Yu >>> > > >>> > > >>> > > On Tue, 21 Jun 2022 at 22:55, OpenInx wrote: >>> > > >>> > > > +1 (binding) >>> > > > >>> > > > 1. Download the source tarball, signature (.asc), and checksum >>> > (.sha512): >>> > > > OK >>> > > > 2. Import gpg keys: download KEYS and run gpg --import >>> > > > /path/to/downloaded/KEYS : OK >>> > > > 3. Verify the signature by running: gpg --verify >>> > > > hbase-thirdparty-4.1.1-src.tar.gz.asc : OK >>> > > > 4. Verify the checksum by running: shasum -a 512 >>> > > > hbase-thirdparty-4.1.1-src.tar.gz : OK >>> > > > 5. Untar the archive and go into the source directory: tar xzvf >>> > > > hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK >>> > > > 6. Run RAT checks to validate license headers: mvn >>> apache-rat:check: OK >>> > > > 7. Build and test the project: mvn install (use Java 8) : OK >>> > > > >>> > > > Thanks Duo Zhang for the great release work, and thanks all for the >>> > > > verification! >>> > > > >>> > > > On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha >> > >>> > > wrote: >>> > > > >>> > > > > +1 (binding) >>> > > > > >>> > > > > * Signature: ok >>> > > > > * Checksum : ok >>> > > > > * Rat check (1.8.0_202): ok >>> > > > > - mvn clean apache-rat:check >>> > > > > * Built from source (1.8.0_202): ok >>> > > > > - mvn clean install -DskipTests >>> > > > > >>> > > > > Thanks, >>> > > > > Xiaolin Ha >>> > > > > >>> > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： >>> > > > > >>> > > > > > Please vote on this Apache hbase thirdparty release candidate, >>> > > > > > hbase-thirdparty-4.1.1RC0 >>> > > > > > >>> > > > > > The VOTE will remain open for at least 72 hours. >>> > > > > > >>> > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 >>> > > > > > [ ] -1 Do not release this package because ... >>> > > > > > >>> > > > > > The tag to be voted on is 4.1.1RC0: >>> > > > > > >>> > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 >>> > > > > > >>> > > > > > This tag currently points to git reference >>> > > > > > >>> > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 >>> > > > > > >>> > > > > > 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.1RC0/ >>> > > > > > >>> > > > > > Maven artifacts are available in a staging repository at: >>> > > > > > >>> > > > > > >>> > > > > >>> > > >>> https://repository.apache.org/content/repositories/orgapachehbase-1488/ >>> > > > > > >>> > > > > > Artifacts were signed with the 9AD2AE49 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 >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> >>
Re: [VOTE] Merge feature branch HBASE-26913 to master/branch-2
Left some comments on the PR. PTAL. Thanks. 张铎(Duo Zhang) 于2022年6月22日周三 10:08写道： > Skimmed the design doc, I think it is a very useful feature for detecting > and debugging replication inconsistencies. Good job. > > And since the feature is default off, I'm optimistic that we can merge it > first and then keep polishing it in the future, as it will not affect the > normal write and replication flow. > > Let me take a look at the PR and report back here. The first suggestion is > that, please use lower case table names, as all our system tables are in > lower case :) > > Thanks for the great work. > > Andrew Purtell 于2022年6月22日周三 06:29写道： > >> +1 >> >> > On Jun 21, 2022, at 10:07 AM, Rushabh Shah >> > >> wrote: >> > >> > Hi everyone, >> > >> > I'm writing this request to propose a merge of HBASE-26913[1] >> "Replication >> > Observability Framework" to master and branch-2. >> > The goal is to persist replication related metadata to newly created >> hbase >> > tables to reduce MTTD (Mean Time To Detect) and >> > MTTR (Mean Time To Repair) replication inconsistencies between Primary >> and >> > DR clusters. >> > The design doc is here[2]. >> > >> > We have created 2 new hbase tables, REPLICATION.WALEVENTTRACKER and >> > REPLICATION.SINK_TRACKER. The first table >> > will store all the WAL events (ACTIVE, ROLLING, ROLLED) along with >> metadata >> > (wal name, wal length, region server name, timestamp) >> > from all region servers. We have introduced a new chore called >> > ReplicationMarkerChore which will create special marker/sentinel rows >> > periodically (which is configurable) and inject them directly to WAL. >> This >> > marker rows will be handled specially and replicated to >> > sink cluster and will be persisted to REPLICATION.SINK_TRACKER table. >> > >> > Highlights >> > * The entire feature is configurable. Defaults to false. >> > * A new section is added to the HBase book which covers the feature and >> how >> > to use it. >> > >> > The vote will open for at least 72 hours. >> > Please vote: >> > [+1]Merge the changes from HBASE-26913 to master/branch-2 >> > [+/-0] Neutral >> > [-1]Disagree (please include actionable feedback) >> > >> > 1. https://issues.apache.org/jira/browse/HBASE-26913 >> > 2. >> > >> https://docs.google.com/document/d/14oZ5ssY28hvJaQD_Jg9kWX7LfUKUyyU2PCA93PPzVko/edit#heading=h.9oum2kn0zj5r >> > >> > >> > Thanks, >> > Rushabh >> >
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
With 6 binding +1s and no -1, the vote passes. Let me finish the release. Thanks all for voting and helping! 张铎(Duo Zhang) 于2022年6月22日周三 10:16写道： > Here is my own +1. > > Yu Li 于2022年6月21日周二 23:24写道： > >> Thanks for the quick reply Duo, makes sense to me. >> >> And thanks for driving this release. >> >> Best Regards, >> Yu >> >> >> On Tue, 21 Jun 2022 at 23:17, 张铎(Duo Zhang) >> wrote: >> >> > Thanks Yu. >> > >> > We do not write release note for HBASE-26893(my fault) so the generate >> > RELEASENOTES.md does not have the release note for this change. >> > >> > I thought the title just tells everything so I did not add a release >> note >> > for it... >> > >> > Anyway, not a blocker this time. In the future will rememer to always >> add a >> > release note for an issue when we bump a dependency. >> > >> > Thanks. >> > >> > Yu Li 于2022年6月21日周二 23:02写道： >> > >> > > +1 (binding) >> > > >> > > Checked the diff between 4.1.0 and 4.1.1-rc0: *OK* ( >> > > >> https://github.com/apache/hbase-thirdparty/compare/rel/4.1.0...4.1.1RC0) >> > > Checked release note and changes: *Minor Update Required* >> > > - It seems we should also include HBASE-26893 (jackson updated to >> 2.13.3) >> > > into release note (RELEASENOTES.md) >> > > Checked sums and signatures: *OK* >> > > Maven clean install from source (8u121): *OK* >> > > Checked the jars in the staging repo: *OK* >> > > >> > > Best Regards, >> > > Yu >> > > >> > > >> > > On Tue, 21 Jun 2022 at 22:55, OpenInx wrote: >> > > >> > > > +1 (binding) >> > > > >> > > > 1. Download the source tarball, signature (.asc), and checksum >> > (.sha512): >> > > > OK >> > > > 2. Import gpg keys: download KEYS and run gpg --import >> > > > /path/to/downloaded/KEYS : OK >> > > > 3. Verify the signature by running: gpg --verify >> > > > hbase-thirdparty-4.1.1-src.tar.gz.asc : OK >> > > > 4. Verify the checksum by running: shasum -a 512 >> > > > hbase-thirdparty-4.1.1-src.tar.gz : OK >> > > > 5. Untar the archive and go into the source directory: tar xzvf >> > > > hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK >> > > > 6. Run RAT checks to validate license headers: mvn >> apache-rat:check: OK >> > > > 7. Build and test the project: mvn install (use Java 8) : OK >> > > > >> > > > Thanks Duo Zhang for the great release work, and thanks all for the >> > > > verification! >> > > > >> > > > On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha >> > > wrote: >> > > > >> > > > > +1 (binding) >> > > > > >> > > > > * Signature: ok >> > > > > * Checksum : ok >> > > > > * Rat check (1.8.0_202): ok >> > > > > - mvn clean apache-rat:check >> > > > > * Built from source (1.8.0_202): ok >> > > > > - mvn clean install -DskipTests >> > > > > >> > > > > Thanks, >> > > > > Xiaolin Ha >> > > > > >> > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： >> > > > > >> > > > > > Please vote on this Apache hbase thirdparty release candidate, >> > > > > > hbase-thirdparty-4.1.1RC0 >> > > > > > >> > > > > > The VOTE will remain open for at least 72 hours. >> > > > > > >> > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 >> > > > > > [ ] -1 Do not release this package because ... >> > > > > > >> > > > > > The tag to be voted on is 4.1.1RC0: >> > > > > > >> > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 >> > > > > > >> > > > > > This tag currently points to git reference >> > > > > > >> > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 >> > > > > > >> > > > > > 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.1RC0/ >> > > > > > >> > > > > > Maven artifacts are available in a staging repository at: >> > > > > > >> > > > > > >> > > > > >> > > >> https://repository.apache.org/content/repositories/orgapachehbase-1488/ >> > > > > > >> > > > > > Artifacts were signed with the 9AD2AE49 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 >> > > > > > >> > > > > >> > > > >> > > >> > >> >
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
Here is my own +1. Yu Li 于2022年6月21日周二 23:24写道： > Thanks for the quick reply Duo, makes sense to me. > > And thanks for driving this release. > > Best Regards, > Yu > > > On Tue, 21 Jun 2022 at 23:17, 张铎(Duo Zhang) wrote: > > > Thanks Yu. > > > > We do not write release note for HBASE-26893(my fault) so the generate > > RELEASENOTES.md does not have the release note for this change. > > > > I thought the title just tells everything so I did not add a release note > > for it... > > > > Anyway, not a blocker this time. In the future will rememer to always > add a > > release note for an issue when we bump a dependency. > > > > Thanks. > > > > Yu Li 于2022年6月21日周二 23:02写道： > > > > > +1 (binding) > > > > > > Checked the diff between 4.1.0 and 4.1.1-rc0: *OK* ( > > > > https://github.com/apache/hbase-thirdparty/compare/rel/4.1.0...4.1.1RC0) > > > Checked release note and changes: *Minor Update Required* > > > - It seems we should also include HBASE-26893 (jackson updated to > 2.13.3) > > > into release note (RELEASENOTES.md) > > > Checked sums and signatures: *OK* > > > Maven clean install from source (8u121): *OK* > > > Checked the jars in the staging repo: *OK* > > > > > > Best Regards, > > > Yu > > > > > > > > > On Tue, 21 Jun 2022 at 22:55, OpenInx wrote: > > > > > > > +1 (binding) > > > > > > > > 1. Download the source tarball, signature (.asc), and checksum > > (.sha512): > > > > OK > > > > 2. Import gpg keys: download KEYS and run gpg --import > > > > /path/to/downloaded/KEYS : OK > > > > 3. Verify the signature by running: gpg --verify > > > > hbase-thirdparty-4.1.1-src.tar.gz.asc : OK > > > > 4. Verify the checksum by running: shasum -a 512 > > > > hbase-thirdparty-4.1.1-src.tar.gz : OK > > > > 5. Untar the archive and go into the source directory: tar xzvf > > > > hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK > > > > 6. Run RAT checks to validate license headers: mvn apache-rat:check: > OK > > > > 7. Build and test the project: mvn install (use Java 8) : OK > > > > > > > > Thanks Duo Zhang for the great release work, and thanks all for the > > > > verification! > > > > > > > > On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha > > > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > * Signature: ok > > > > > * Checksum : ok > > > > > * Rat check (1.8.0_202): ok > > > > > - mvn clean apache-rat:check > > > > > * Built from source (1.8.0_202): ok > > > > > - mvn clean install -DskipTests > > > > > > > > > > Thanks, > > > > > Xiaolin Ha > > > > > > > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > > > > > > > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > > > > hbase-thirdparty-4.1.1RC0 > > > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > > > > > > [ ] -1 Do not release this package because ... > > > > > > > > > > > > The tag to be voted on is 4.1.1RC0: > > > > > > > > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > > > > > > > > > > > This tag currently points to git reference > > > > > > > > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > > > > > > > > > > > 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.1RC0/ > > > > > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > > > > > > > > > > > Artifacts were signed with the 9AD2AE49 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 > > > > > > > > > > > > > > > > > > > > >
Re: [VOTE] First release candidate for hbase 3.0.0-alpha-3 is available for download
Thanks Andrew! No hurry :) Let me finish the hbase-thirdparty release first. Andrew Purtell 于2022年6月22日周三 06:24写道： > We may need some time to give this a proper look among our other work. I > will need some time, a few days. > > > On Jun 20, 2022, at 8:41 AM, 张铎 wrote: > > > > Remind. > > > > We need some votes here to make progress on the 3.0.0 release~ > > > > 张铎(Duo Zhang) 于2022年6月16日周四 00:05写道： > > > >> Please vote on this Apache hbase release candidate, > >> hbase-3.0.0-alpha-3RC0 > >> > >> The VOTE will remain open for at least 72 hours. > >> > >> [ ] +1 Release this package as Apache hbase 3.0.0-alpha-3 > >> [ ] -1 Do not release this package because ... > >> > >> The tag to be voted on is 3.0.0-alpha-3RC0: > >> > >> https://github.com/apache/hbase/tree/3.0.0-alpha-3RC0 > >> > >> This tag currently points to git reference > >> > >> b3657484850f9fa9679f2186bf53e7df768f21c7 > >> > >> 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/3.0.0-alpha-3RC0/ > >> > >> Maven artifacts are available in a staging repository at: > >> > >> > https://repository.apache.org/content/repositories/orgapachehbase-1487/ > >> > >> Artifacts were signed with the 9AD2AE49 key which can be found in: > >> > >> https://downloads.apache.org/hbase/KEYS > >> > >> 3.0.0-alpha-3 is the second alpha release for our 3.0.0 major release > line. > >> HBase 3.0.0 includes the following big feature/changes: > >> Synchronous Replication > >> OpenTelemetry Tracing > >> Distributed MOB Compaction > >> Backup and Restore > >> Move RSGroup balancer to core > >> Reimplement sync client on async client > >> CPEPs on shaded proto > >> Move the logging framework from log4j to log4j2 > >> Decouple region replication and general replication framework, and > >> also make region replication can work when SKIP_WAL is used > >> > >> Notice that this is not a production ready release. It is used to let > our > >> users try and test the new major release, to get feedback before the > final > >> GA release is out. > >> So please do NOT use it in production. Just try it and report back > >> everything you find unusual. > >> > >> And this time we will not include CHANGES.md and RELEASENOTE.md > >> in our source code, you can find it on the download site. For getting > these > >> two files for old releases, please go to > >> > >> https://archive.apache.org/dist/hbase/ > >> > >> To learn more about Apache hbase, please see > >> > >> http://hbase.apache.org/ > >> > >> Thanks, > >> Your HBase Release Manager > >> >
Re: [VOTE] Merge feature branch HBASE-26913 to master/branch-2
Skimmed the design doc, I think it is a very useful feature for detecting and debugging replication inconsistencies. Good job. And since the feature is default off, I'm optimistic that we can merge it first and then keep polishing it in the future, as it will not affect the normal write and replication flow. Let me take a look at the PR and report back here. The first suggestion is that, please use lower case table names, as all our system tables are in lower case :) Thanks for the great work. Andrew Purtell 于2022年6月22日周三 06:29写道： > +1 > > > On Jun 21, 2022, at 10:07 AM, Rushabh Shah > > > wrote: > > > > Hi everyone, > > > > I'm writing this request to propose a merge of HBASE-26913[1] > "Replication > > Observability Framework" to master and branch-2. > > The goal is to persist replication related metadata to newly created > hbase > > tables to reduce MTTD (Mean Time To Detect) and > > MTTR (Mean Time To Repair) replication inconsistencies between Primary > and > > DR clusters. > > The design doc is here[2]. > > > > We have created 2 new hbase tables, REPLICATION.WALEVENTTRACKER and > > REPLICATION.SINK_TRACKER. The first table > > will store all the WAL events (ACTIVE, ROLLING, ROLLED) along with > metadata > > (wal name, wal length, region server name, timestamp) > > from all region servers. We have introduced a new chore called > > ReplicationMarkerChore which will create special marker/sentinel rows > > periodically (which is configurable) and inject them directly to WAL. > This > > marker rows will be handled specially and replicated to > > sink cluster and will be persisted to REPLICATION.SINK_TRACKER table. > > > > Highlights > > * The entire feature is configurable. Defaults to false. > > * A new section is added to the HBase book which covers the feature and > how > > to use it. > > > > The vote will open for at least 72 hours. > > Please vote: > > [+1]Merge the changes from HBASE-26913 to master/branch-2 > > [+/-0] Neutral > > [-1]Disagree (please include actionable feedback) > > > > 1. https://issues.apache.org/jira/browse/HBASE-26913 > > 2. > > > https://docs.google.com/document/d/14oZ5ssY28hvJaQD_Jg9kWX7LfUKUyyU2PCA93PPzVko/edit#heading=h.9oum2kn0zj5r > > > > > > Thanks, > > Rushabh >
[jira] [Resolved] (HBASE-27098) Fix link for field comments
[ https://issues.apache.org/jira/browse/HBASE-27098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-27098. -- Fix Version/s: 2.5.0 3.0.0-alpha-4 Hadoop Flags: Reviewed Resolution: Fixed > Fix link for field comments > --- > > Key: HBASE-27098 > URL: https://issues.apache.org/jira/browse/HBASE-27098 > Project: HBase > Issue Type: Bug >Reporter: Tao Li >Assignee: Tao Li >Priority: Minor > Fix For: 2.5.0, 3.0.0-alpha-4 > > > Fix link for field `REJECT_BATCH_ROWS_OVER_THRESHOLD` comments. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (HBASE-27147) Add a hbck2 option to clear emptyRegion from meta
Karthik Palanisamy created HBASE-27147: -- Summary: Add a hbck2 option to clear emptyRegion from meta Key: HBASE-27147 URL: https://issues.apache.org/jira/browse/HBASE-27147 Project: HBase Issue Type: Bug Reporter: Karthik Palanisamy No alternative option in hbck2 to fix empty regions. hbck1 equivalent is "-fixEmptyMetaCells". "Try to fix hbase:meta entries not referencing any region (empty REGIONINFO_QUALIFIER rows)" NOTE: This is an inconsistent meta bug. -- This message was sent by Atlassian Jira (v8.20.7#820007)
Re: [VOTE] Merge feature branch HBASE-26913 to master/branch-2
+1 > On Jun 21, 2022, at 10:07 AM, Rushabh Shah > wrote: > > Hi everyone, > > I'm writing this request to propose a merge of HBASE-26913[1] "Replication > Observability Framework" to master and branch-2. > The goal is to persist replication related metadata to newly created hbase > tables to reduce MTTD (Mean Time To Detect) and > MTTR (Mean Time To Repair) replication inconsistencies between Primary and > DR clusters. > The design doc is here[2]. > > We have created 2 new hbase tables, REPLICATION.WALEVENTTRACKER and > REPLICATION.SINK_TRACKER. The first table > will store all the WAL events (ACTIVE, ROLLING, ROLLED) along with metadata > (wal name, wal length, region server name, timestamp) > from all region servers. We have introduced a new chore called > ReplicationMarkerChore which will create special marker/sentinel rows > periodically (which is configurable) and inject them directly to WAL. This > marker rows will be handled specially and replicated to > sink cluster and will be persisted to REPLICATION.SINK_TRACKER table. > > Highlights > * The entire feature is configurable. Defaults to false. > * A new section is added to the HBase book which covers the feature and how > to use it. > > The vote will open for at least 72 hours. > Please vote: > [+1]Merge the changes from HBASE-26913 to master/branch-2 > [+/-0] Neutral > [-1]Disagree (please include actionable feedback) > > 1. https://issues.apache.org/jira/browse/HBASE-26913 > 2. > https://docs.google.com/document/d/14oZ5ssY28hvJaQD_Jg9kWX7LfUKUyyU2PCA93PPzVko/edit#heading=h.9oum2kn0zj5r > > > Thanks, > Rushabh
Re: [VOTE] First release candidate for hbase 3.0.0-alpha-3 is available for download
We may need some time to give this a proper look among our other work. I will need some time, a few days. > On Jun 20, 2022, at 8:41 AM, 张铎 wrote: > > Remind. > > We need some votes here to make progress on the 3.0.0 release~ > > 张铎(Duo Zhang) 于2022年6月16日周四 00:05写道： > >> Please vote on this Apache hbase release candidate, >> hbase-3.0.0-alpha-3RC0 >> >> The VOTE will remain open for at least 72 hours. >> >> [ ] +1 Release this package as Apache hbase 3.0.0-alpha-3 >> [ ] -1 Do not release this package because ... >> >> The tag to be voted on is 3.0.0-alpha-3RC0: >> >> https://github.com/apache/hbase/tree/3.0.0-alpha-3RC0 >> >> This tag currently points to git reference >> >> b3657484850f9fa9679f2186bf53e7df768f21c7 >> >> 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/3.0.0-alpha-3RC0/ >> >> Maven artifacts are available in a staging repository at: >> >> https://repository.apache.org/content/repositories/orgapachehbase-1487/ >> >> Artifacts were signed with the 9AD2AE49 key which can be found in: >> >> https://downloads.apache.org/hbase/KEYS >> >> 3.0.0-alpha-3 is the second alpha release for our 3.0.0 major release line. >> HBase 3.0.0 includes the following big feature/changes: >> Synchronous Replication >> OpenTelemetry Tracing >> Distributed MOB Compaction >> Backup and Restore >> Move RSGroup balancer to core >> Reimplement sync client on async client >> CPEPs on shaded proto >> Move the logging framework from log4j to log4j2 >> Decouple region replication and general replication framework, and >> also make region replication can work when SKIP_WAL is used >> >> Notice that this is not a production ready release. It is used to let our >> users try and test the new major release, to get feedback before the final >> GA release is out. >> So please do NOT use it in production. Just try it and report back >> everything you find unusual. >> >> And this time we will not include CHANGES.md and RELEASENOTE.md >> in our source code, you can find it on the download site. For getting these >> two files for old releases, please go to >> >> https://archive.apache.org/dist/hbase/ >> >> To learn more about Apache hbase, please see >> >> http://hbase.apache.org/ >> >> Thanks, >> Your HBase Release Manager >>
Re: [VOTE] Merge feature branch HBASE-26913 to master/branch-2
+1, thanks for the excellent work, Rushabh! Due to recent merge conflicts, the PR could not be created from the feature branch against the master branch. Hence here is the final PR against master branch, with individual commits that can be merged commit-by-commit once we have sufficient votes: https://github.com/apache/hbase/pull/4556 On Tue, Jun 21, 2022 at 10:07 AM Rushabh Shah wrote: > Hi everyone, > > I'm writing this request to propose a merge of HBASE-26913[1] "Replication > Observability Framework" to master and branch-2. > The goal is to persist replication related metadata to newly created hbase > tables to reduce MTTD (Mean Time To Detect) and > MTTR (Mean Time To Repair) replication inconsistencies between Primary and > DR clusters. > The design doc is here[2]. > > We have created 2 new hbase tables, REPLICATION.WALEVENTTRACKER and > REPLICATION.SINK_TRACKER. The first table > will store all the WAL events (ACTIVE, ROLLING, ROLLED) along with metadata > (wal name, wal length, region server name, timestamp) > from all region servers. We have introduced a new chore called > ReplicationMarkerChore which will create special marker/sentinel rows > periodically (which is configurable) and inject them directly to WAL. This > marker rows will be handled specially and replicated to > sink cluster and will be persisted to REPLICATION.SINK_TRACKER table. > > Highlights > * The entire feature is configurable. Defaults to false. > * A new section is added to the HBase book which covers the feature and how > to use it. > > The vote will open for at least 72 hours. > Please vote: > [+1]Merge the changes from HBASE-26913 to master/branch-2 > [+/-0] Neutral > [-1]Disagree (please include actionable feedback) > > 1. https://issues.apache.org/jira/browse/HBASE-26913 > 2. > > https://docs.google.com/document/d/14oZ5ssY28hvJaQD_Jg9kWX7LfUKUyyU2PCA93PPzVko/edit#heading=h.9oum2kn0zj5r > > > Thanks, > Rushabh >
[jira] [Resolved] (HBASE-27143) Add hbase-unsafe as a dependency for a MR job triggered by hbase shell
[
https://issues.apache.org/jira/browse/HBASE-27143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tak-Lon (Stephen) Wu resolved HBASE-27143.
--
Fix Version/s: 2.5.0
3.0.0-alpha-3
2.4.13
Hadoop Flags: Reviewed
Resolution: Fixed
commits pushed to master, branch-2, branch-2.5, branch-2.4
> Add hbase-unsafe as a dependency for a MR job triggered by hbase shell
> --
>
> Key: HBASE-27143
> URL: https://issues.apache.org/jira/browse/HBASE-27143
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.5.0, 3.0.0-alpha-3, 2.4.13
>Reporter: Tak-Lon (Stephen) Wu
>Assignee: Tak-Lon (Stephen) Wu
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.13
>
>
> After HBASE-26523, the use of hbase-thirdparty 4.1.0 introduced an new
> dependency of hbase-unsafe that wasn't added as part of the MR job triggered
> by hbase-shell. As such, class not found exception was being emitted when
> executing in distributed mode.
> {code}
> 22/06/21 04:57:15 INFO mapreduce.Job: Task Id :
> attempt_1655784404826_0011_m_00_0, Status : FAILED
> Error: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.unsafe.HBasePlatformDependent
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at org.apache.hadoop.hbase.util.Bytes.(Bytes.java:129)
> at
> org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList$Generator$GeneratorMapper.setup(IntegrationTestBigLinkedList.java:455)
> at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:143)
> at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:799)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:347)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:174)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:423)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1899)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:168)
> {code}
> This task will add it back as part of the job configuration handled by hbase
> internally in addHBaseDependencyJars
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[VOTE] Merge feature branch HBASE-26913 to master/branch-2
Hi everyone, I'm writing this request to propose a merge of HBASE-26913[1] "Replication Observability Framework" to master and branch-2. The goal is to persist replication related metadata to newly created hbase tables to reduce MTTD (Mean Time To Detect) and MTTR (Mean Time To Repair) replication inconsistencies between Primary and DR clusters. The design doc is here[2]. We have created 2 new hbase tables, REPLICATION.WALEVENTTRACKER and REPLICATION.SINK_TRACKER. The first table will store all the WAL events (ACTIVE, ROLLING, ROLLED) along with metadata (wal name, wal length, region server name, timestamp) from all region servers. We have introduced a new chore called ReplicationMarkerChore which will create special marker/sentinel rows periodically (which is configurable) and inject them directly to WAL. This marker rows will be handled specially and replicated to sink cluster and will be persisted to REPLICATION.SINK_TRACKER table. Highlights * The entire feature is configurable. Defaults to false. * A new section is added to the HBase book which covers the feature and how to use it. The vote will open for at least 72 hours. Please vote: [+1]Merge the changes from HBASE-26913 to master/branch-2 [+/-0] Neutral [-1]Disagree (please include actionable feedback) 1. https://issues.apache.org/jira/browse/HBASE-26913 2. https://docs.google.com/document/d/14oZ5ssY28hvJaQD_Jg9kWX7LfUKUyyU2PCA93PPzVko/edit#heading=h.9oum2kn0zj5r Thanks, Rushabh
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
Thanks for the quick reply Duo, makes sense to me. And thanks for driving this release. Best Regards, Yu On Tue, 21 Jun 2022 at 23:17, 张铎(Duo Zhang) wrote: > Thanks Yu. > > We do not write release note for HBASE-26893(my fault) so the generate > RELEASENOTES.md does not have the release note for this change. > > I thought the title just tells everything so I did not add a release note > for it... > > Anyway, not a blocker this time. In the future will rememer to always add a > release note for an issue when we bump a dependency. > > Thanks. > > Yu Li 于2022年6月21日周二 23:02写道： > > > +1 (binding) > > > > Checked the diff between 4.1.0 and 4.1.1-rc0: *OK* ( > > https://github.com/apache/hbase-thirdparty/compare/rel/4.1.0...4.1.1RC0) > > Checked release note and changes: *Minor Update Required* > > - It seems we should also include HBASE-26893 (jackson updated to 2.13.3) > > into release note (RELEASENOTES.md) > > Checked sums and signatures: *OK* > > Maven clean install from source (8u121): *OK* > > Checked the jars in the staging repo: *OK* > > > > Best Regards, > > Yu > > > > > > On Tue, 21 Jun 2022 at 22:55, OpenInx wrote: > > > > > +1 (binding) > > > > > > 1. Download the source tarball, signature (.asc), and checksum > (.sha512): > > > OK > > > 2. Import gpg keys: download KEYS and run gpg --import > > > /path/to/downloaded/KEYS : OK > > > 3. Verify the signature by running: gpg --verify > > > hbase-thirdparty-4.1.1-src.tar.gz.asc : OK > > > 4. Verify the checksum by running: shasum -a 512 > > > hbase-thirdparty-4.1.1-src.tar.gz : OK > > > 5. Untar the archive and go into the source directory: tar xzvf > > > hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK > > > 6. Run RAT checks to validate license headers: mvn apache-rat:check: OK > > > 7. Build and test the project: mvn install (use Java 8) : OK > > > > > > Thanks Duo Zhang for the great release work, and thanks all for the > > > verification! > > > > > > On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha > > wrote: > > > > > > > +1 (binding) > > > > > > > > * Signature: ok > > > > * Checksum : ok > > > > * Rat check (1.8.0_202): ok > > > > - mvn clean apache-rat:check > > > > * Built from source (1.8.0_202): ok > > > > - mvn clean install -DskipTests > > > > > > > > Thanks, > > > > Xiaolin Ha > > > > > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > > > > > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > > > hbase-thirdparty-4.1.1RC0 > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > > > > > [ ] -1 Do not release this package because ... > > > > > > > > > > The tag to be voted on is 4.1.1RC0: > > > > > > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > > > > > > > > > This tag currently points to git reference > > > > > > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > > > > > > > > > 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.1RC0/ > > > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > > > > > > > > > Artifacts were signed with the 9AD2AE49 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 > > > > > > > > > > > > > > >
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
Thanks Yu. We do not write release note for HBASE-26893(my fault) so the generate RELEASENOTES.md does not have the release note for this change. I thought the title just tells everything so I did not add a release note for it... Anyway, not a blocker this time. In the future will rememer to always add a release note for an issue when we bump a dependency. Thanks. Yu Li 于2022年6月21日周二 23:02写道： > +1 (binding) > > Checked the diff between 4.1.0 and 4.1.1-rc0: *OK* ( > https://github.com/apache/hbase-thirdparty/compare/rel/4.1.0...4.1.1RC0) > Checked release note and changes: *Minor Update Required* > - It seems we should also include HBASE-26893 (jackson updated to 2.13.3) > into release note (RELEASENOTES.md) > Checked sums and signatures: *OK* > Maven clean install from source (8u121): *OK* > Checked the jars in the staging repo: *OK* > > Best Regards, > Yu > > > On Tue, 21 Jun 2022 at 22:55, OpenInx wrote: > > > +1 (binding) > > > > 1. Download the source tarball, signature (.asc), and checksum (.sha512): > > OK > > 2. Import gpg keys: download KEYS and run gpg --import > > /path/to/downloaded/KEYS : OK > > 3. Verify the signature by running: gpg --verify > > hbase-thirdparty-4.1.1-src.tar.gz.asc : OK > > 4. Verify the checksum by running: shasum -a 512 > > hbase-thirdparty-4.1.1-src.tar.gz : OK > > 5. Untar the archive and go into the source directory: tar xzvf > > hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK > > 6. Run RAT checks to validate license headers: mvn apache-rat:check: OK > > 7. Build and test the project: mvn install (use Java 8) : OK > > > > Thanks Duo Zhang for the great release work, and thanks all for the > > verification! > > > > On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha > wrote: > > > > > +1 (binding) > > > > > > * Signature: ok > > > * Checksum : ok > > > * Rat check (1.8.0_202): ok > > > - mvn clean apache-rat:check > > > * Built from source (1.8.0_202): ok > > > - mvn clean install -DskipTests > > > > > > Thanks, > > > Xiaolin Ha > > > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > > > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > > hbase-thirdparty-4.1.1RC0 > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > > > > [ ] -1 Do not release this package because ... > > > > > > > > The tag to be voted on is 4.1.1RC0: > > > > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > > > > > > > This tag currently points to git reference > > > > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > > > > > > > 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.1RC0/ > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > > > > > > > Artifacts were signed with the 9AD2AE49 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 > > > > > > > > > >
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
+1 (binding) Checked the diff between 4.1.0 and 4.1.1-rc0: *OK* ( https://github.com/apache/hbase-thirdparty/compare/rel/4.1.0...4.1.1RC0) Checked release note and changes: *Minor Update Required* - It seems we should also include HBASE-26893 (jackson updated to 2.13.3) into release note (RELEASENOTES.md) Checked sums and signatures: *OK* Maven clean install from source (8u121): *OK* Checked the jars in the staging repo: *OK* Best Regards, Yu On Tue, 21 Jun 2022 at 22:55, OpenInx wrote: > +1 (binding) > > 1. Download the source tarball, signature (.asc), and checksum (.sha512): > OK > 2. Import gpg keys: download KEYS and run gpg --import > /path/to/downloaded/KEYS : OK > 3. Verify the signature by running: gpg --verify > hbase-thirdparty-4.1.1-src.tar.gz.asc : OK > 4. Verify the checksum by running: shasum -a 512 > hbase-thirdparty-4.1.1-src.tar.gz : OK > 5. Untar the archive and go into the source directory: tar xzvf > hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK > 6. Run RAT checks to validate license headers: mvn apache-rat:check: OK > 7. Build and test the project: mvn install (use Java 8) : OK > > Thanks Duo Zhang for the great release work, and thanks all for the > verification! > > On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha wrote: > > > +1 (binding) > > > > * Signature: ok > > * Checksum : ok > > * Rat check (1.8.0_202): ok > > - mvn clean apache-rat:check > > * Built from source (1.8.0_202): ok > > - mvn clean install -DskipTests > > > > Thanks, > > Xiaolin Ha > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > hbase-thirdparty-4.1.1RC0 > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > > > [ ] -1 Do not release this package because ... > > > > > > The tag to be voted on is 4.1.1RC0: > > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > > > > > This tag currently points to git reference > > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > > > > > 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.1RC0/ > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > > > > > Artifacts were signed with the 9AD2AE49 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 > > > > > >
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
+1 (binding) 1. Download the source tarball, signature (.asc), and checksum (.sha512): OK 2. Import gpg keys: download KEYS and run gpg --import /path/to/downloaded/KEYS : OK 3. Verify the signature by running: gpg --verify hbase-thirdparty-4.1.1-src.tar.gz.asc : OK 4. Verify the checksum by running: shasum -a 512 hbase-thirdparty-4.1.1-src.tar.gz : OK 5. Untar the archive and go into the source directory: tar xzvf hbase-thirdparty-4.1.1-src.tar.gz && cd hbase-thirdparty-4.1.1: OK 6. Run RAT checks to validate license headers: mvn apache-rat:check: OK 7. Build and test the project: mvn install (use Java 8) : OK Thanks Duo Zhang for the great release work, and thanks all for the verification! On Tue, Jun 21, 2022 at 7:00 PM Xiaolin Ha wrote: > +1 (binding) > > * Signature: ok > * Checksum : ok > * Rat check (1.8.0_202): ok > - mvn clean apache-rat:check > * Built from source (1.8.0_202): ok > - mvn clean install -DskipTests > > Thanks, > Xiaolin Ha > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > > > Please vote on this Apache hbase thirdparty release candidate, > > hbase-thirdparty-4.1.1RC0 > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > > [ ] -1 Do not release this package because ... > > > > The tag to be voted on is 4.1.1RC0: > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > > > This tag currently points to git reference > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > > > 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.1RC0/ > > > > Maven artifacts are available in a staging repository at: > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > > > Artifacts were signed with the 9AD2AE49 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 > > >
[jira] [Reopened] (HBASE-26981) The CPU usage of the regionserver node where the meta table is located is too high
[ https://issues.apache.org/jira/browse/HBASE-26981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-26981: --- > The CPU usage of the regionserver node where the meta table is located is too > high > -- > > Key: HBASE-26981 > URL: https://issues.apache.org/jira/browse/HBASE-26981 > Project: HBase > Issue Type: Bug > Components: hbase-connectors >Affects Versions: 2.3.4 >Reporter: zhengsicheng >Priority: Major > Attachments: image-2022-04-27-20-24-33-252.png, > image-2022-04-27-20-45-09-227.png, image-2022-04-28-09-59-40-567.png, jstack > > > When the read and write pressure is high, the CPU usage of the meta table > node is too high > !image-2022-04-28-09-59-40-567.png! > > !image-2022-04-27-20-24-33-252.png! -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (HBASE-27146) Avoid CellUtil.cloneRow in MetaCellComparator
Duo Zhang created HBASE-27146: - Summary: Avoid CellUtil.cloneRow in MetaCellComparator Key: HBASE-27146 URL: https://issues.apache.org/jira/browse/HBASE-27146 Project: HBase Issue Type: Improvement Reporter: Duo Zhang In HBASE-26981, a flame graph shows that we spend a lot of CPUs in CellUtils.cloneXXX. Since we need to split the row to different parts when comparing, we can not use ByteBuffer compare directly, but as least, we should try to avoid copy the content when the Cell is stored in a ByteBuffer. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (HBASE-27145) Mark ByteBufferUtils as IA.Private
[
https://issues.apache.org/jira/browse/HBASE-27145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-27145.
---
Fix Version/s: (was: 3.0.0-alpha-4)
Resolution: Duplicate
Ah, looking at the wrong branch...
On master we have already marked it as IA.Private...
> Mark ByteBufferUtils as IA.Private
> --
>
> Key: HBASE-27145
> URL: https://issues.apache.org/jira/browse/HBASE-27145
> Project: HBase
> Issue Type: Sub-task
> Components: API
>Reporter: Duo Zhang
>Priority: Major
> Labels: beginner, trivial
>
> As the javadoc says
> {code}
> /**
> * Utility functions for working with byte buffers, such as reading/writing
> variable-length long
> * numbers.
> * @deprecated This class will become IA.Private in HBase 3.0. Downstream
> folks shouldn't use it.
> */
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (HBASE-27145) Mark ByteBufferUtils as IA.Private
Duo Zhang created HBASE-27145:
-
Summary: Mark ByteBufferUtils as IA.Private
Key: HBASE-27145
URL: https://issues.apache.org/jira/browse/HBASE-27145
Project: HBase
Issue Type: Sub-task
Components: API
Reporter: Duo Zhang
Fix For: 3.0.0-alpha-4
As the javadoc says
{code}
/**
* Utility functions for working with byte buffers, such as reading/writing
variable-length long
* numbers.
* @deprecated This class will become IA.Private in HBase 3.0. Downstream folks
shouldn't use it.
*/
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (HBASE-27144) Add bulkload rpc
zhengsicheng created HBASE-27144: Summary: Add bulkload rpc Key: HBASE-27144 URL: https://issues.apache.org/jira/browse/HBASE-27144 Project: HBase Issue Type: Improvement Reporter: zhengsicheng Assignee: zhengsicheng -- This message was sent by Atlassian Jira (v8.20.7#820007)
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_202): ok - mvn clean apache-rat:check * Built from source (1.8.0_202): ok - mvn clean install -DskipTests Thanks, Xiaolin Ha 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > Please vote on this Apache hbase thirdparty release candidate, > hbase-thirdparty-4.1.1RC0 > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 4.1.1RC0: > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > This tag currently points to git reference > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > 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.1RC0/ > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > Artifacts were signed with the 9AD2AE49 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 >
Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download
+1 (binding) * Signature: ok * Checksum : ok * Rat check (1.8.0_322): ok - mvn clean apache-rat:check * Built from source (1.8.0_322): ok - mvn clean install -DskipTests Thanks, Peter On Tue, Jun 21, 2022 at 7:59 AM Guanghao Zhang wrote: > +1 (binding) > > * Signature: ok > * Checksum : ok > * Rat check (1.8.0_301): ok > - mvn clean apache-rat:check > * Built from source (1.8.0_301): ok > - mvn clean install -DskipTests > > 张铎(Duo Zhang) 于2022年6月20日周一 23:40写道： > > > See https://github.com/apache/hbase/pull/4552 > > > > After modifying some code in HBase, mainly because of a behavior change > in > > jetty, we can pass all the UTs when depending on hbase-thirdparty-4.1.1. > > > > 张铎(Duo Zhang) 于2022年6月18日周六 23:04写道： > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > hbase-thirdparty-4.1.1RC0 > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1 > > > [ ] -1 Do not release this package because ... > > > > > > The tag to be voted on is 4.1.1RC0: > > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0 > > > > > > This tag currently points to git reference > > > > > > d674246a75e1d7d1d4c5ee09a2567bbfa1cec022 > > > > > > 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.1RC0/ > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1488/ > > > > > > Artifacts were signed with the 9AD2AE49 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 > > > > > >
