Any insights on this?

On Thu, Feb 5, 2026 at 8:35 AM rammohan ganapavarapu <
[email protected]> wrote:

> I am talking about the server, I see the docs mentioning jdk17 support and
> jdk17 which will be EOL in 2026, so I am trying to see if zookeeper
> supports jdk21 and jdk25.
>
> Thanks,
>
>
>
>
> On Thu, Feb 5, 2026 at 1:47 AM Enrico Olivelli <[email protected]>
> wrote:
>
>> Are you asking about the Client or on the Server ?
>>
>> I am pretty sure that you can use the Client on JDK8 onwards without any
>> particular issue.
>>
>> Enrico
>>
>>
>> Il giorno gio 5 feb 2026 alle ore 09:37 Jungwook Song <[email protected]>
>> ha scritto:
>>
>>> Hi Rammohan,
>>>
>>> According to the official documentation at
>>> https://zookeeper.apache.org/releases.html (
>>> https://zookeeper.apache.org/releases.html), ZooKeeper has officially
>>> supported JDK 17 since version 3.8.0.
>>>
>>> Best regards,
>>>
>>> JW SONG
>>>
>>>
>>> 2026년 2월 5일 (목) AM 4:37, rammohan ganapavarapu <[email protected]>님이
>>> 작성:
>>>
>>>> Hi,
>>>>
>>>> I am looking for an apache zookeeper JDK support matrix, I know the
>>>> documentation says this "ZooKeeper runs in Java, release 1.8 or greater
>>>> (JDK 8 LTS, JDK 11 LTS, JDK 12 - Java 9 and 10 are not supported)." But
>>>> is
>>>> it officially supported and tested against  JDK17, JDK21 and JDK25 ? If
>>>> so,
>>>> do we have any documentation to confirm that?
>>>>
>>>> Thanks,
>>>>
>>>
>>>
>>> --
>>> JUNGWOOK SONG
>>> Ph. D. in Computer Engineering
>>> CTO, Director
>>>
>>> [image: cert_admin.png] [image: cert_developer.png]
>>>
>>> Spitha Inc.
>>> 43, Daesagwan-ro, Yongsan-gu, 04401
>>> SEOUL, SOUTH KOREA
>>> M) +82.010.3706.8386
>>> E) [email protected]
>>>
>>> spitha.io
>>>
>>>
>>>
>>>
>>> The content of this email is confidential and intended for the recipient
>>> specified in message only. It is strictly forbidden to share any part of
>>> this message with any third party, without a written consent of the sender.
>>> If you received this message by mistake, please reply to this message and
>>> follow with its deletion, so that we can ensure such a mistake does not
>>> occur in the future.
>>>
>>>
>>>
>>>

Reply via email to