[HADOOP-18862] [JDK17] MiniYarnClusters don't launch in hadoop-aws integration tests

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 23/Aug/23 10:46
• Updated: 20/Oct/23 09:19

Description

I've tried running hadoop-aws tests under java17; everything which tries to launch a MiniYarnCluster fails because google guice is trying to stuff in java.land module that is now forbidden

Caused by: java.lang.ExceptionInInitializerError: Exception com.google.inject.internal.cglib.core.$CodeGenerationException: java.lang.reflect.InaccessibleObjectException-->Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @7ee7980d [in thread "Thread-109"]

short term fix is to add the params to the surefire and failsafe jvm launcher to allow access

--add-opens java.base/java.lang=ALL-UNNAMED

I don't know if updating guice will make it go away completely. if it doesn't then the history server itself needs to be launched with this

rather than just add an option for hadoop-aws, we ought to consider a general cross-module variable for junit.jvm.options which is set everywhere; the base impl is "" and a java profile could add the new stuff

Issue Links

• depends upon: MAPREDUCE-7449 Add add-opens flag to container launch commands on JDK17 nodes