[jira] [Resolved] (HBASE-26046) [JDK17] Add a JDK17 profile

[Duo Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-26046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-26046.
---
Resolution: Implemented

Done via HBASE-27870.

> [JDK17] Add a JDK17 profile
> ---
>
> Key: HBASE-26046
> URL: https://issues.apache.org/jira/browse/HBASE-26046
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Wei-Chiu Chuang
>Priority: Major
>
> While HBase builds fine with JDK17, tests fail because a number of Java SDK 
> modules are no longer exposed to unnamed modules by default. We need to open 
> them up.
> Without which, the tests fail for errors like:
> {noformat}
> [ERROR] Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.469 
> s <<< FAILURE! - in org.apache.hadoop.hbase.rest.model.TestNamespacesModel
> [ERROR] org.apache.hadoop.hbase.rest.model.TestNamespacesModel.testBuildModel 
>  Time elapsed: 0.273 s  <<< ERROR!
> java.lang.ExceptionInInitializerError
> at 
> org.apache.hadoop.hbase.rest.model.TestNamespacesModel.(TestNamespacesModel.java:43)
> Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make 
> protected final java.lang.Class 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int) throws 
> java.lang.ClassFormatError accessible: module java.base does not "opens 
> java.lang" to unnamed module @56ef9176
> at 
> org.apache.hadoop.hbase.rest.model.TestNamespacesModel.(TestNamespacesModel.java:43)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (HBASE-27870) Eliminate the 'WARNING: package jdk.internal.util.random not in java.base' when running UTs with jdk11

[Duo Zhang (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-27870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-27870.
---
Fix Version/s: 2.6.0
   3.0.0-alpha-4
   2.5.5
   2.4.18
 Hadoop Flags: Reviewed
   Resolution: Fixed

Pushed to branch-2.4+.

Thanks [~tangtianhang] for reviewing!

> Eliminate the 'WARNING: package jdk.internal.util.random not in java.base' 
> when running UTs with jdk11
> --
>
> Key: HBASE-27870
> URL: https://issues.apache.org/jira/browse/HBASE-27870
> Project: HBase
>  Issue Type: Improvement
>  Components: build, pom, test
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.5, 2.4.18
>
>
> When fixing a jdk17 issue, we add a
> --add-opens java.base/jdk.internal.util.random=ALL-UNNAMED
> line in our pom when running UTs with jdk11+, so it will also be applied for 
> jdk11, but we only need this for jdk17, on jdk11, it will generate a warning, 
> as described in the title.
> We should try some maven magics to fix this.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HBASE-27874) Problem in flakey generated report causes pre-commit run to fail

[Wellington Chevreuil (Jira)]

Wellington Chevreuil created HBASE-27874:


 Summary: Problem in flakey generated report causes pre-commit run 
to fail
 Key: HBASE-27874
 URL: https://issues.apache.org/jira/browse/HBASE-27874
 Project: HBase
  Issue Type: Bug
  Components: build
Reporter: Wellington Chevreuil
Assignee: Wellington Chevreuil


Have noticed the UT pre-commit run failed on this latest PR for branch-2 with 
the below:
{noformat}
Thu May 18 10:37:32 AM UTC 2023
cd 
/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-5241/yetus-jdk8-hadoop2-check/src/hbase-server
/opt/maven/bin/mvn --batch-mode 
-Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-5241/yetus-m2/hbase-branch-2-patch-1
 --threads=4 
-Djava.io.tmpdir=/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-5241/yetus-jdk8-hadoop2-check/src/target
 -DHBasePatchProcess -PrunAllTests 
-Dtest.exclude.pattern=**/regionserver.TestMetricsRegionServer.java,**/master.procedure.TestSnapshotProcedureRSCrashes.java,**/security.access.TestAccessController.java,**/conf.TestConfigurationManagerWARNING:
 package jdk.internal.util.random not in 
java.base.java,**/io.hfile.bucket.TestPrefetchPersistence.java,**/client.TestFromClientSide3.java,**/replication.TestReplicationMetricsforUI.java,**/io.hfile.bucket.TestBucketCache.java,**/replication.regionserver.TestReplicationValueCompressedWAL.java,**/master.procedure.TestHBCKSCP.java,**/http.TestInfoServersACL.java,**/io.hfile.bucket.TestBucketCachePersister.java,**/replication.TestReplicationKillSlaveRS.java,**/regionserver.TestClearRegionBlockCache.java,**/master.TestUnknownServers.java,**/replication.TestReplicationKillSlaveRSWithSeparateOldWALs.java,**/quotas.TestClusterScopeQuotaThrottle.java,**/io.hfile.TestBlockEvictionOnRegionMovement.java,**/replication.regionserver.TestMetaRegionReplicaReplicationEndpoint.java,**/regionserver.TestRegionReplicas.java,**/coprocessor.TestCoprocessorEndpointTracing.java,**/master.region.TestMasterRegionCompaction.java,**/io.hfile.TestPrefetchRSClose.java
 -Dsurefire.firstPartForkCount=0.5C -Dsurefire.secondPartForkCount=0.5C clean 
test -fae


[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  0.861 s (Wall Clock)
[INFO] Finished at: 2023-05-18T10:37:34Z
[INFO] 
[ERROR] Unknown lifecycle phase "jdk.internal.util.random". You must specify a 
valid lifecycle phase or a goal in the format : or 
:[:]:. Available 
lifecycle phases are: validate, initialize, generate-sources, process-sources, 
generate-resources, process-resources, compile, process-classes, 
generate-test-sources, process-test-sources, generate-test-resources, 
process-test-resources, test-compile, process-test-classes, test, 
prepare-package, package, pre-integration-test, integration-test, 
post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, 
pre-site, site, post-site, site-deploy. -> [Help 1]
[ERROR] 
{noformat}
Note the "{+}**/conf.TestConfigurationManagerWARNING: package 
jdk.internal.util.random not in java.base.java{+}" passed as one of the 
supposedly flakey tests. Looking around our build scripts, I figured we pull 
the list of flakey from the "{+}excludes{+}" artifact generated by the latest 
"find flakey" build. It seems the [latest branch-2 
run|https://ci-hbase.apache.org/job/HBase-Find-Flaky-Tests/job/branch-2/1063/artifact/output/excludes]
 generated this artifact with the wrong name already:

{noformat}
**/replication.TestReplicationMetricsforUI.java,**/conf.TestConfigurationManagerWARNING:
 package jdk.internal.util.random not in 
java.base.java,**/master.region.TestMasterRegionCompaction.java,**/regionserver.TestRegionReplicas.java,**/replication.regionserver.TestReplicationValueCompressedWAL.java,**/coprocessor.TestCoprocessorEndpointTracing.java,**/quotas.TestClusterScopeQuotaThrottle.java,**/replication.TestReplicationKillSlaveRSWithSeparateOldWALs.java,**/client.TestFromClientSide3.java,**/io.hfile.TestBlockEvictionOnRegionMovement.java,**/io.hfile.bucket.TestPrefetchPersistence.java,**/regionserver.TestMetricsRegionServer.java,**/io.hfile.bucket.TestBucketCachePersister.java,**/regionserver.TestClearRegionBlockCache.java,**/master.procedure.TestHBCKSCP.java,**/replication.regionserver.TestMetaRegionReplicaReplicationEndpoint.java,**/security.access.TestAccessController.java,**/io.hfile.bucket.TestBucketCache.java,**/io.hfile.TestPrefetchRSClose.java,**/replication.TestReplicationKillSlaveRS.java,**/master.TestUnknownServers.java,**/http.TestInfoServersACL.java
{noformat}

Digging deeper, found that the "find flakey" build checks the UT output of 
latest nightly and flakey builds, to p

Re: [Discuss] Adding support for mapping namespaces to Region Server Groups

[唐天航]

Hi Rajeshbabu,

I'm not sure but could HBASE-24032
 solve your problem?

rajeshb...@apache.org  于2023年5月3日周三 13:03写道：


rajeshb...@apache.org  于2023年5月3日周三 13:03写道：

> Hi,
>
> Currently RS groups supports mapping the tables to a rsgroup and there are
> commands and APIs to move the tables in a namespace to rsgroup. But what
> ever the tables created after moving the tables needs to get added to RS
> group explicitly otherwise those will be under default rs group.
>
> Would be better to support directly mapping the namespaces ( higher
> granular level than tables) to rs group so that tables under the namespace
> directly gets assigned to the rs group. This will simplify the operations
> when using namespaces and rs groups together for better isolation.
>
> If it's fine will raise corresponding JIRAs and work on it.
>
>
> Thanks,
> Rajeshbabu.
>

[jira] [Created] (HBASE-27873) Asyncfs may print too many WARN logs when replace writer

[tianhang tang (Jira)]

tianhang tang created HBASE-27873:
-

 Summary: Asyncfs may print too many WARN logs when replace writer
 Key: HBASE-27873
 URL: https://issues.apache.org/jira/browse/HBASE-27873
 Project: HBase
  Issue Type: Improvement
Reporter: tianhang tang
Assignee: tianhang tang
 Attachments: image-2023-05-18-15-51-33-823.png

When we use Asyncfs for WAL, could see many WARN logs like this:

!image-2023-05-18-15-51-33-823.png!

namenode#complete is a relatively heavy operation, and sometimes it takes 
seconds.

So we can reduce this log, just as what 
[DFSOutputStream#completeFile|[http://example.com|https://github.com/apache/hadoop/blob/706d88266abcee09ed78fbaa0ad5f74d818ab0e9/hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DFSOutputStream.java#L975]]
 do.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)