Re: Releases News Inquiry

2023-11-29 Thread Richard Zowalla
Hi,

according to ASF policies, we send release announcements to:

user@storm.apache.org
d...@storm.apache.org
annou...@apache.org

So if you are subscribed to user@, it should be sufficient.

Gruß
Richard


Am Donnerstag, dem 30.11.2023 um 08:02 +0100 schrieb Alexandre
Vermeerbergen:
> Hello,
> 
> How about this page
> https://storm.apache.org/2023/11/22/storm260-released.html, does it
> meet your need ?
> 
> Thanks,
> Alexandre
> 
> Le jeu. 30 nov. 2023 à 08:00, patricia lee  a
> écrit :
> > 
> > Hi,
> > 
> > I am new to storm. I just wanted to ask if the news on announcement
> > of new release (other than the official website) is there a
> > specific email distro where we can receive news when a new version
> > of storm is about to release?
> > 
> > The reason is that we have to create a lifecycle process within the
> > team and distro subscription for new releases is needed.
> > 
> > 
> > Regards,
> > Pat
> > 



Re: Releases News Inquiry

2023-11-29 Thread Alexandre Vermeerbergen
Hello,

How about this page
https://storm.apache.org/2023/11/22/storm260-released.html, does it
meet your need ?

Thanks,
Alexandre

Le jeu. 30 nov. 2023 à 08:00, patricia lee  a écrit :
>
> Hi,
>
> I am new to storm. I just wanted to ask if the news on announcement of new 
> release (other than the official website) is there a specific email distro 
> where we can receive news when a new version of storm is about to release?
>
> The reason is that we have to create a lifecycle process within the team and 
> distro subscription for new releases is needed.
>
>
> Regards,
> Pat
>


Releases News Inquiry

2023-11-29 Thread patricia lee
Hi,

I am new to storm. I just wanted to ask if the news on announcement of new
release (other than the official website) is there a specific email distro
where we can receive news when a new version of storm is about to release?

The reason is that we have to create a lifecycle process within the team
and distro subscription for new releases is needed.


Regards,
Pat


Re: Running Storm with Java 21 runtime... works !

2023-11-29 Thread Rui Abreu
Great to hear, Alexandre!
Cheers

On Wed, 29 Nov 2023 at 20:07, Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:

> Hello,
>
> Just for the Storm's users community information: since today this
> morning (CET), I am running my pre-production Storm 2.6.0 cluster (10+
> topologies relying on storm-kafka, storm-hdfs, etc) using Java 21
> runtime (more precisely using OpenJ9 21.0.1 milestone 1 on Linux x64
> on Redhat).
>
>   Java 21 is used for Nimbus, Nimbus UI, all Supervisor and Logview
> processes, and for Zookeepers, and of course to execute the topologies
> code.
>   I had no need to fix anything.
>
>   One (maybe) important detail: all topologies' code was build with
> JDK 17, and it was previously running with IBM Semeru 17.0.8.1 (alias
> OpenJ9).
>
>   I will keep this setup on the preproduction cluster for say 2 months
> before No/NoGo for production use, carefully monitoring all stats
> (topologies latencies, capacities, CPU/Memory/IOPS usage on Supervisor
> nodes, etc) - so far so good but it's too early to conclude.
>
> Note: I won't try compiling our topologies with JDK21 before a while,
> but it looks like Storm code can be compiled with JDK21 thanks to
> Richard Zowalla recent attention to make it possible!
>
> If others have similar experience to share, they are welcome to let us
> know !
>
> Thanks,
> Alexandre
>


Running Storm with Java 21 runtime... works !

2023-11-29 Thread Alexandre Vermeerbergen
Hello,

Just for the Storm's users community information: since today this
morning (CET), I am running my pre-production Storm 2.6.0 cluster (10+
topologies relying on storm-kafka, storm-hdfs, etc) using Java 21
runtime (more precisely using OpenJ9 21.0.1 milestone 1 on Linux x64
on Redhat).

  Java 21 is used for Nimbus, Nimbus UI, all Supervisor and Logview
processes, and for Zookeepers, and of course to execute the topologies
code.
  I had no need to fix anything.

  One (maybe) important detail: all topologies' code was build with
JDK 17, and it was previously running with IBM Semeru 17.0.8.1 (alias
OpenJ9).

  I will keep this setup on the preproduction cluster for say 2 months
before No/NoGo for production use, carefully monitoring all stats
(topologies latencies, capacities, CPU/Memory/IOPS usage on Supervisor
nodes, etc) - so far so good but it's too early to conclude.

Note: I won't try compiling our topologies with JDK21 before a while,
but it looks like Storm code can be compiled with JDK21 thanks to
Richard Zowalla recent attention to make it possible!

If others have similar experience to share, they are welcome to let us know !

Thanks,
Alexandre