[
https://issues.apache.org/jira/browse/HBASE-26038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786500#comment-17786500
]
Bryan Beaudreault commented on HBASE-26038:
-------------------------------------------
[~weichiu] [~tangtianhang] are you still working on this? I believe multiple
members of the community are running jdk17 in production. The remaining issues
are build related, maybe the only blocker is HBASE-27949. I'd like to get this
closed out so that we can assert jdk17 support in our docs, given community
usage.
> Support JDK17
> -------------
>
> Key: HBASE-26038
> URL: https://issues.apache.org/jira/browse/HBASE-26038
> Project: HBase
> Issue Type: New Feature
> Reporter: Wei-Chiu Chuang
> Priority: Major
>
> JDK 17 is the next Java LTS, coming out this September.
> It brings a number of goodies. One of which is the production-ready ZGC
> (available since JDK15). (as well as the Shenandoah GC, available since JDK15)
> After September 2021, there will be three Java LTS versions: Java 8, Java 11
> and Java 17. Java 8 will still be the mainstream SDK in the foreseeable
> future, so I am not looking to take advantage of the new APIs that are only
> available in JDK17. This jira aims to support HBase on all three JDK LTS.
> Porting HBase to JDK17 is not a big hurdle. HBase (master branch) builds
> successfully on JDK17. A few tests fail mostly due to the new (more strict)
> Java module isolation enforcement. I have a small PoC that I will post here
> in the coming days.
> What I am trying to achieve is to add an experimental support for JDK17. It
> will be interesting to benchmark HBase on ZGC and Shenandoah and determine if
> we should set our default GC to them. By then, we'll be able to claim
> production-ready support.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
