[GitHub] [pulsar] nicoloboschi commented on issue #15207: PIP-156: Build and Run Pulsar Server on Java 17

[GitBox <gi...@apache.org>]

nicoloboschi commented on issue #15207:
URL: https://github.com/apache/pulsar/issues/15207#issuecomment-1103958580

   @heesung-sn, thanks for formalizing this plan.
   IIUC the tasks to do are:
   - move the jdk target to 17 for the build except for the client modules
   - merge my pull for moving CI to jdk17 (https://github.com/apache/pulsar/pull/14355)
   
   I think we should clarify that we support only jdk17 for all the components and jd8, jdk11 and jdk17 for the java client. (we'll need a matrix job in the CI to test the different jdk versions)
   
   We, at Datastax, have run multiple benchmarks and it looks like the performance are really improved (also using Shenandoah GC). @dave2wave  is doing this kind of tests and he can share more details.
   
   My main worry is about connectors. Pulsar builtin connectors are not - all - well tested and some of them are not run by the CI and we don’t know if they will work correctly with jdk17.
   There are some tricky issues with JDK17 due to the "new" [JDK internals encapsulation rules](https://openjdk.java.net/jeps/403) but we fixed them all in the latest weeks and the Pulsar master actually works well.
   
   >We expect Pulsar dependency libraries such as BookKeeper and ZooKeeper to work well on Java17
   
   For BookKeeper, we started a similar work to build and test BookKeeper with JDK17. The work is still not completed but I'm not aware of any issues (even tho, I believe that nobody is using BK with JDK17).
   
   


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org