ctubbsii opened a new issue, #5139: URL: https://github.com/apache/accumulo/issues/5139
Java 17 has some nice new features, and earlier LTS versions of Java are EOL. For new development branches, we should have the option of using newer Java features. Java 17 has records, for example, that are of particular interest. Also of personal interest to me, is the ability to use the more robust switch statements. The main blocker for this is that there is an unknown issue with starting Hadoop Yarn for MapReduce on a Java 17 VM. So, we can't put Accumulo byte-code in to anything going through MapReduce until that's figured out. We do know that the HDFS itself works on JDK 17, and the HDFS client does as well, because we've been running that in our ITs for awhile now. So, it's just whatever the issue is with Yarn, as far as I can tell. For testing, https://github.com/apache/fluo-uno/pull/297 circumvented the problem by skipping starting Yarn when running on with Java newer than version 11, but that's not a suitable solution for any production deployment of Accumulo (it's not even a suitable solution for testing, if you want to test MapReduce). The issue may be quite trivial... I'm not sure. Some initial investigation occurred in [Slack](https://the-asf.slack.com/archives/CERNB8NDC/p1712870215519739) that may hint at some Java module options need to be added to the yarn env script, or something similar, but there may be more to it than that. For reference, Hadoop tracking ticket for Java 17 support is [here](https://issues.apache.org/jira/browse/HADOOP-17177). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
