Unsubscribe me

Thanks & Regards
Sri Tummala


On Wed, Aug 5, 2026, 12:09 PM Gianluca Bonetti <[email protected]>
wrote:

> Hello
>
> I have been running software on Apache Ignite 2.18 with Java 17 for years.
>
> In my experience, upgrading from 2.17 to 2.18 required no extra steps, I
> just used the latest Ignite version. Of course, you must shut down your
> cluster to upgrade, as rolling updates are only supported in GridGain.
>
> Apache Ignite 2.18 does not list Java 21 as a supported platform:
> https://ignite.apache.org/docs/ignite2/latest/quick-start/java
>
> https://ignite.apache.org/docs/ignite2/latest/quick-start/java#running-ignite-with-java-11-or-later
>
> As Apache Ignite is community-supported, I would not suggest running it on
> an unsupported Java version. Otherwise, you will be on your own for
> support, if that is something you can afford.
>
> Cheers
> Gianluca Bonetti
>
>
> On Wed, 5 Aug 2026 at 05:49, BEELA GAYATRI via user <
> [email protected]> wrote:
>
>> TCS Confidential
>>
>> Hi @[email protected] <[email protected]>,
>>
>>
>>       We are currently using *Apache Ignite 2.17.0* with *Java 11* in
>> our application. As part of our technology upgrade roadmap, we are planning
>> to migrate the application to *Java 21*.
>> We would like to understand whether *Apache Ignite 2.18.0* is fully
>> compatible and supported with *Java 21*, and if there are any known
>> limitations, prerequisites, or recommended configurations for this
>> combination.
>> Migrating to *Apache Ignite 3.x* is not our preferred option at this
>> stage, as it would require significant architectural and application-level
>> changes. Therefore, our objective is to remain on the *Ignite 2.x*
>> stream while upgrading the Java runtime.
>> Could you please provide guidance or best practices for upgrading from 
>> *Apache
>> Ignite 2.17.0 (Java 11)* to *Apache Ignite 2.18.0 (Java 21)*?
>>
>> Thanks & Regards,
>> Gayatri Beela
>>
>> =====-----=====-----=====
>> Notice: The information contained in this e-mail
>> message and/or attachments to it may contain
>> confidential or privileged information. If you are
>> not the intended recipient, any dissemination, use,
>> review, distribution, printing or copying of the
>> information contained in this e-mail message
>> and/or attachments to it are strictly prohibited. If
>> you have received this communication in error,
>> please notify us by reply e-mail or telephone and
>> immediately and permanently delete the message
>> and any attachments. Thank you
>>
>>

Reply via email to