[jira] [Created] (HBASE-25522) Remove deprecated methods in ReplicationPeerConfig
Baiqiang Zhao created HBASE-25522: - Summary: Remove deprecated methods in ReplicationPeerConfig Key: HBASE-25522 URL: https://issues.apache.org/jira/browse/HBASE-25522 Project: HBase Issue Type: Sub-task Affects Versions: 3.0.0-alpha-1 Reporter: Baiqiang Zhao Assignee: Baiqiang Zhao Fix For: 3.0.0-alpha-1 HBASE-19576 introduce ReplicationPeerConfigBuilder to set the value of ReplicationPeerConfig. The deprecated methods in ReplicationPeerConfig should be removed in 3.x. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Third release candidate for HBase 2.4.1 (RC2) is available
+1 (binding) * hash: good * signature: good (gpg: Note: This key has expired!) * api compare looks good * built from src 'mvn clean install -DskipTests assembly:single -Dhadoop.profile=3.0 -Prelease' with 'openjdk version "11.0.9" 2020-10-20' * Poked around the UI (We need to fix this: 2.4.1, revision=Unknown as our version in UI) * Loaded up 3M rows w/ pe in MR mode. Verified all loaded. * Poked around in the shell S On Fri, Jan 15, 2021 at 1:54 PM Andrew Purtell wrote: > [ Thanks to Viraj Jasani for ensuring an accurate change log and for > scripting a tool to do the same. ] > > Please vote on this Apache hbase release candidate, hbase-2.4.1RC2. > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache hbase 2.4.1 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 2.4.1RC2: > > https://github.com/apache/hbase/tree/2.4.1RC2 > > 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.4.1RC2/ > > The JIRA change log for this release can be found at: > > https://s.apache.org/0nopx > > Temporary Maven artifacts are available in the staging repository: > > > https://repository.apache.org/content/repositories/orgapachehbase-1434/ > > Artifacts were signed with the apurt...@apache.org key which can be found > in: > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > The API compatibility report for this RC can be found at: > > > > https://dist.apache.org/repos/dist/dev/hbase/2.4.1RC2/api_compare_2.4.0_to_2.4.1RC2.html > > To learn more about Apache HBase, please see > > http://hbase.apache.org/ > > Thanks, > Your HBase Release Manager >
Re: [VOTE] HBase 2.3.4 release candidate (RC4) is available
+1 (binding) * Signature: good * Checksum : good * Built from src: mvn clean install -DskipTests assembly:single -Dhadoop.profile=3.0 -Prelease * Checked UI * Loaded 3m w/ pe running local MR * Verified loaded 3m w/ MR and w/o MR * Poked about in the shell S On Wed, Jan 20, 2021 at 11:20 AM Nick Dimiduk wrote: > +1 > > * Signature: ok > * Checksum : ok > * Rat check (1.8.0_275): ok > - mvn clean apache-rat:check -D skipTests > * Rat check (11.0.9.1): ok > - mvn clean apache-rat:check -D skipTests -D hadoop.profile=3.0 > * Built from source (1.8.0_275): ok > - mvn clean install -D skipTests -DskipTests > * Built from source (11.0.9.1): ok > - mvn clean install -D skipTests -D hadoop.profile=3.0 -DskipTests > * Unit tests pass (1.8.0_275): ok > - mvn package -P runAllTests -D skipTests > -Dsurefire.rerunFailingTestsCount=3 > * Unit tests pass (11.0.9.1): ok > - mvn package -P runAllTests -D skipTests -D hadoop.profile=3.0 > -Dsurefire.rerunFailingTestsCount=3 > * bin tarball launches on JDK 11.0.8+10. > * Revision number on webUI matches tag in git. > * Jenkins builds have been broken lately, but Viraj noted the WIP > fix. > > On Thu, Jan 14, 2021 at 7:04 PM Huaxiang Sun > wrote: > > > Please vote on this Apache hbase release candidate, > > > > hbase-2.3.4RC4 > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > [ ] +1 Release this package as Apache hbase 2.3.4 > > > > [ ] -1 Do not release this package because ... > > > > > > The tag to be voted on is 2.3.4RC4: > > > > > > https://github.com/apache/hbase/tree/2.3.4RC4 > > > > > > 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.3.4RC4/ > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1433/ > > > > > > Artifacts were signed with the huaxiang...@apache.org key which can be > > found in: > > > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > > > To learn more about Apache hbase, please see > > > > > > http://hbase.apache.org/ > > > > > > Thanks, > > > > Your HBase Release Manager > > >
Re: [VOTE] HBase 2.3.4 release candidate (RC4) is available
+1 * Signature: ok * Checksum : ok * Rat check (1.8.0_275): ok - mvn clean apache-rat:check -D skipTests * Rat check (11.0.9.1): ok - mvn clean apache-rat:check -D skipTests -D hadoop.profile=3.0 * Built from source (1.8.0_275): ok - mvn clean install -D skipTests -DskipTests * Built from source (11.0.9.1): ok - mvn clean install -D skipTests -D hadoop.profile=3.0 -DskipTests * Unit tests pass (1.8.0_275): ok - mvn package -P runAllTests -D skipTests -Dsurefire.rerunFailingTestsCount=3 * Unit tests pass (11.0.9.1): ok - mvn package -P runAllTests -D skipTests -D hadoop.profile=3.0 -Dsurefire.rerunFailingTestsCount=3 * bin tarball launches on JDK 11.0.8+10. * Revision number on webUI matches tag in git. * Jenkins builds have been broken lately, but Viraj noted the WIP fix. On Thu, Jan 14, 2021 at 7:04 PM Huaxiang Sun wrote: > Please vote on this Apache hbase release candidate, > > hbase-2.3.4RC4 > > > The VOTE will remain open for at least 72 hours. > > > [ ] +1 Release this package as Apache hbase 2.3.4 > > [ ] -1 Do not release this package because ... > > > The tag to be voted on is 2.3.4RC4: > > > https://github.com/apache/hbase/tree/2.3.4RC4 > > > 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.3.4RC4/ > > > Maven artifacts are available in a staging repository at: > > > https://repository.apache.org/content/repositories/orgapachehbase-1433/ > > > Artifacts were signed with the huaxiang...@apache.org key which can be > found in: > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > To learn more about Apache hbase, please see > > > http://hbase.apache.org/ > > > Thanks, > > Your HBase Release Manager >
[jira] [Resolved] (HBASE-25368) Filter out more invalid encoded name in isEncodedRegionName(byte[] regionName)
[
https://issues.apache.org/jira/browse/HBASE-25368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun resolved HBASE-25368.
--
Fix Version/s: 3.0.0-alpha-1
Resolution: Fixed
> Filter out more invalid encoded name in isEncodedRegionName(byte[]
> regionName)
> ---
>
> Key: HBASE-25368
> URL: https://issues.apache.org/jira/browse/HBASE-25368
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Reporter: Huaxiang Sun
>Assignee: Huaxiang Sun
>Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> {code:java}
> public static boolean isEncodedRegionName(byte[] regionName) {
> // If not parseable as region name, presume encoded. TODO: add stringency;
> e.g. if hex.
> return parseRegionNameOrReturnNull(regionName) == null && regionName.length
> <= MD5_HEX_LENGTH;
> }
> Right now, if it passes in an table name, it still thinks it is a encoded
> region name and will result in unnecessary registry query for meta regions.
> This can be avoided if table names can be filtered out early in this
> method.{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-25521) Change ChoreService and ScheduledChore to IA.Private
Duo Zhang created HBASE-25521: - Summary: Change ChoreService and ScheduledChore to IA.Private Key: HBASE-25521 URL: https://issues.apache.org/jira/browse/HBASE-25521 Project: HBase Issue Type: Task Components: util Reporter: Duo Zhang Follow up issue for HBASE-25509. We are not providing a general scheduling library, so these two classes should not be IA.Public. User can just use other more powerful scheduling libraries. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25509) ChoreService.cancelChore will not call ScheduledChore.cleanup which may lead to resource leak
[ https://issues.apache.org/jira/browse/HBASE-25509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25509. --- Fix Version/s: 2.4.2 2.5.0 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.4+ Thanks [~vjasani] for reviewing. > ChoreService.cancelChore will not call ScheduledChore.cleanup which may lead > to resource leak > - > > Key: HBASE-25509 > URL: https://issues.apache.org/jira/browse/HBASE-25509 > Project: HBase > Issue Type: Sub-task > Components: util >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25329) Dump region hashes in logs for the regions that are stuck in transition for more than a configured amount of time
[ https://issues.apache.org/jira/browse/HBASE-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-25329. -- Fix Version/s: 1.7.0 Resolution: Fixed All backports completed. Thanks [~caroliney14] for the contribution. > Dump region hashes in logs for the regions that are stuck in transition for > more than a configured amount of time > - > > Key: HBASE-25329 > URL: https://issues.apache.org/jira/browse/HBASE-25329 > Project: HBase > Issue Type: Improvement >Reporter: Caroline >Assignee: Caroline >Priority: Minor > Fix For: 3.0.0-alpha-1, 1.7.0, 2.2.7, 2.5.0, 2.3.5, 2.4.1 > > Attachments: HBASE-25329.branch-1.000.patch, > HBASE-25329.branch-2.000.patch, HBASE-25329.master.000.patch > > > We have metrics for number of RITs as well as number of RITs above a certain > threshold, but we don't have any way of keeping track of the region hashes of > those RITs. It would be beneficial to emit those region hashes as a metric, > as well as log them, so that we don't accidentally lose this information for > debugging the RIT at a later tiime. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-25329) Dump region hashes in logs for the regions that are stuck in transition for more than a configured amount of time
[ https://issues.apache.org/jira/browse/HBASE-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani reopened HBASE-25329: -- Reopening for branch-1 backport. > Dump region hashes in logs for the regions that are stuck in transition for > more than a configured amount of time > - > > Key: HBASE-25329 > URL: https://issues.apache.org/jira/browse/HBASE-25329 > Project: HBase > Issue Type: Improvement >Reporter: Caroline >Assignee: Caroline >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.2.7, 2.5.0, 2.4.1, 2.3.5 > > Attachments: HBASE-25329.branch-1.000.patch, > HBASE-25329.branch-2.000.patch, HBASE-25329.master.000.patch > > > We have metrics for number of RITs as well as number of RITs above a certain > threshold, but we don't have any way of keeping track of the region hashes of > those RITs. It would be beneficial to emit those region hashes as a metric, > as well as log them, so that we don't accidentally lose this information for > debugging the RIT at a later tiime. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] HBase 2.3.4 release candidate (RC4) is available
+1 * Signature: ok * Checksum : ok * Rat check (1.8.0_265): ok - mvn clean apache-rat:check * Built from source (1.8.0_265): ok - mvn clean install -DskipTests * Unit tests pass (1.8.0_265): ok - mvn package -P runAllTests -Dsurefire.rerunFailingTestsCount=3 LTT 1M rows: ok Thanks, Peter On Tue, Jan 19, 2021 at 6:45 PM Huaxiang Sun wrote: > Hi Folks, > The 2.3.4RC4 vote has been up for 4 days, so far, we got 1 +1 > (binding), 1 +1 (non-binding). When you have a moment, please vote. > > Thanks > Your HBase Release Manager > > On Sun, Jan 17, 2021 at 10:08 PM Huaxiang Sun > wrote: > > > >Put 2.4.0 to a 15 node cluster (3 masters, 12 region servers), run itbll > > with serverKilling chaos monkey. > > > > > Added 3 billions row, it’ll finished successfully (verified). > > > > > > A typo, I put 2.3.4RC4 to the cluster and itbll run successfully. > > > > On Sat, Jan 16, 2021 at 10:45 PM Viraj Jasani > wrote: > > > >> +1 (binding) > >> > >> * Signature: ok > >> * Checksum : ok > >> * Rat check (1.8.0_171): ok > >> - mvn clean apache-rat:check > >> * Built from source (1.8.0_171): ok > >> - mvn clean install -DskipTests > >> * Unit tests pass (1.8.0_171): ok > >> - mvn package -P runSmallTests > >> * All tests: branch-2.3 nightly runs look good > >> (one consistent failure with TestSplitWALManager which is not > >> part of this RC and the work is in progress to resolve it) > >> * CHANGELOG: ok > >> * Release Notes: ok > >> * CRUD: ok > >> > >> > >> On 2021/01/15 03:03:47, Huaxiang Sun wrote: > >> > Please vote on this Apache hbase release candidate, > >> > > >> > hbase-2.3.4RC4 > >> > > >> > > >> > The VOTE will remain open for at least 72 hours. > >> > > >> > > >> > [ ] +1 Release this package as Apache hbase 2.3.4 > >> > > >> > [ ] -1 Do not release this package because ... > >> > > >> > > >> > The tag to be voted on is 2.3.4RC4: > >> > > >> > > >> > https://github.com/apache/hbase/tree/2.3.4RC4 > >> > > >> > > >> > 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.3.4RC4/ > >> > > >> > > >> > Maven artifacts are available in a staging repository at: > >> > > >> > > >> > > >> https://repository.apache.org/content/repositories/orgapachehbase-1433/ > >> > > >> > > >> > Artifacts were signed with the huaxiang...@apache.org key which can > be > >> > found in: > >> > > >> > > >> > https://dist.apache.org/repos/dist/release/hbase/KEYS > >> > > >> > > >> > To learn more about Apache hbase, please see > >> > > >> > > >> > http://hbase.apache.org/ > >> > > >> > > >> > Thanks, > >> > > >> > Your HBase Release Manager > >> > > >> > > >
