[jira] [Resolved] (HBASE-27489) Fix several problems after HBASE-27304
[ https://issues.apache.org/jira/browse/HBASE-27489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27489. --- Fix Version/s: 2.6.0 3.0.0-alpha-4 Hadoop Flags: Reviewed Resolution: Fixed Pushed to master and branch-2. Thanks [~heliangjun]! > Fix several problems after HBASE-27304 > -- > > Key: HBASE-27489 > URL: https://issues.apache.org/jira/browse/HBASE-27489 > Project: HBase > Issue Type: Bug > Components: master, regionserver >Reporter: Liangjun He >Assignee: Liangjun He >Priority: Minor > Fix For: 2.6.0, 3.0.0-alpha-4 > > > In the HBASE-27304, we support using IP to expose master/rs service to > client. But there are several problems that need to be fixed, see > #[4732|https://github.com/apache/hbase/pull/4732] for details. This issue is > used to track and fix these problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27562) Publish SBOM artifacts
Dongjoon Hyun created HBASE-27562: - Summary: Publish SBOM artifacts Key: HBASE-27562 URL: https://issues.apache.org/jira/browse/HBASE-27562 Project: HBase Issue Type: Improvement Components: java Affects Versions: 3.0.0-alpha-4 Reporter: Dongjoon Hyun -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27561) hbase.master.port is ignored in processing of hbase.masters
Andrew Kyle Purtell created HBASE-27561: --- Summary: hbase.master.port is ignored in processing of hbase.masters Key: HBASE-27561 URL: https://issues.apache.org/jira/browse/HBASE-27561 Project: HBase Issue Type: Bug Components: Client Affects Versions: 2.5.2 Reporter: Andrew Kyle Purtell Assignee: Andrew Kyle Purtell Fix For: 3.0.0-alpha-4, 2.4.16, 2.5.3 Setting of hbase.master.port is ignored in default processing of hbase.masters. For example, hbase.masters=localhost hbase.master.port=8100 "Server at localhost:16000" is in the failed servers list" hbase.masters=localhost:8100 hbase.master.port=8100 All is well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HBASE-27560) CatalogJanitor consistencyCheck cannot report the hole on last region if next table is disabled in meta
Leo89 created HBASE-27560: - Summary: CatalogJanitor consistencyCheck cannot report the hole on last region if next table is disabled in meta Key: HBASE-27560 URL: https://issues.apache.org/jira/browse/HBASE-27560 Project: HBase Issue Type: Bug Components: hbck2 Affects Versions: 2.5.2, 2.4.15, 3.0.0-alpha-3 Reporter: Leo89 When doing metaTableConsistencyCheck with ReportMakingVisitor, it will skip to check disabled table. When table before the disabled table in meta has a hole on last region, it cannot be added to holes pairs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27554) Test failures on branch-2.4 with corrupted exclude list
[
https://issues.apache.org/jira/browse/HBASE-27554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-27554.
---
Resolution: Fixed
Recent nightly tests were successful on branch-2.4 after the cleanup.
> Test failures on branch-2.4 with corrupted exclude list
> ---
>
> Key: HBASE-27554
> URL: https://issues.apache.org/jira/browse/HBASE-27554
> Project: HBase
> Issue Type: Bug
> Components: jenkins
>Affects Versions: 2.4.16
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
>
> Nightly builds and PRs on branch-2.4 are failing with an invalid exclude list.
> Executed unit test command:
> {code:java}
> /opt/maven/bin/mvn --batch-mode
> -Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4944/yetus-m2/hbase-branch-2.4-patch-0
> --threads=4
> -Djava.io.tmpdir=/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4944/yetus-jdk8-hadoop2-check/src/target
> -DHBasePatchProcess -PrunAllTests
> -Dtest.exclude.pattern=**/replication.regionserver.TestMetaRegionReplicaReplicationEndpoint.java,**/client.TestMetaRegionLocationCache.java,**/master.balancer.TestStochasticLoadBalancerRegionReplicaWithRacks.java,**/replication.TestZKReplicationQueueStorageWARNING:
> All illegal access operations will be denied in a future
> release.java,**/replication.regionserver.TestBasicWALEntryStreamFSHLog.java
> -Dsurefire.firstPartForkCount=0.5C -Dsurefire.secondPartForkCount=0.5C clean
> test -fae {code}
> The latest exclude list contains "WARNING: All illegal access operations will
> be denied in a future release" and maven treats this as a new parameter. As a
> result unit tests are failing on CI that rely on the exclude list.
> [https://ci-hbase.apache.org/job/HBase-Find-Flaky-Tests/job/branch-2.4/lastSuccessfulBuild/artifact/output/excludes/*view*/]
> {noformat}
> **/replication.regionserver.TestMetaRegionReplicaReplicationEndpoint.java,**/client.TestMetaRegionLocationCache.java,**/master.balancer.TestStochasticLoadBalancerRegionReplicaWithRacks.java,**/replication.TestZKReplicationQueueStorageWARNING:
> All illegal access operations will be denied in a future
> release.java,**/replication.regionserver.TestBasicWALEntryStreamFSHLog.java
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
