Re: Nightlies and Snapshot artifacts of Storm

Thanks! 🚀 Am Mi., 6. Dez. 2023 um 09:13 Uhr schrieb Richard Zowalla : > Hi all, > > I am glad to announce, that we are now publishing automatic SNAPSHOT > builds (aka nightlies) from the master branch at a daily basis. > > You can find the tar.gz / zip files here: > > https://nightlies.apache.org

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

Thanks, good to know! We are currently on Java 17 and storm 2.4.0 but plan upgrading to 21 in a couple of months. Am Mi., 29. Nov. 2023 um 23:06 Uhr schrieb Rui Abreu : > Great to hear, Alexandre! > Cheers > > On Wed, 29 Nov 2023 at 20:07, Alexandre Vermeerbergen < > avermeerber...@gmail.com> wro

Re: [ANNOUNCE] Apache Storm 2.6.0 Released

Great update, many thanks storm team! Am Do., 23. Nov. 2023 um 09:53 Uhr schrieb Julien Nioche : > The Apache Storm community is pleased to announce the release of Apache > Storm version 2.6.0. > > Apache Storm is a distributed, fault-tolerant, and high-performance > realtime computation system t

Re: [HELP NEEDED] Future of external Storm modules

Hi Richard, thanks for setting up the poll, I think this is a very meaningful step to help storm development focusing its resources best. Regarding the vote: how should one vote? Does yes/green checkmark mean "I am actively using the external module" or does it mean "I am okay with the module bei

Re: [DISCUSSION] Apache Storm and moving to the Attic

+1 for keeping Apache Storm maintained and +1 for Taylor as PMC! Am Fr., 3. Feb. 2023 um 14:58 Uhr schrieb Alexandre Vermeerbergen < avermeerber...@gmail.com>: > +1 for whatever makes Apache Storm to be maintained as long as > possible, including my time if needed ! > > Alexandre > > Le ven. 3 fé

Re: ZeroMQ in Storm 2

Hi Binh, to my knowledge ZeroMQ is no longer used in storm. >From what you describe it seems there is a problem with acking/failing in your topology (could be downstream bolts do not ack or fail in all cases) and tuples get emitted until max pending is exhausted, then start failing when they hit

Re: Getting error Class cannot be created (missing no-arg constructor): com.datastax.driver.core.LocalDate

t; Regards, > -Anandh Kumar > > > On Thu, Sep 16, 2021 at 12:50 PM Jonas Krauss wrote: > >> Hi Anandh, >> >> according to the error message, your class lacks a simple no arguments >> constructor like this: >> >> public LocalDate() {} >> >>

Re: Getting error Class cannot be created (missing no-arg constructor): com.datastax.driver.core.LocalDate

Hi Anandh, according to the error message, your class lacks a simple no arguments constructor like this: public LocalDate() {} Kryo needs this for working properly when doing deserialization I think. Give it a try! Jonas Am Do., 16. Sept. 2021 um 09:05 Uhr schrieb Anandh Kumar < anandhz...@gm

Re: Our topology is running significantly slower in Storm 2.2.0 than in 1.2.0

Hi Trude, one important difference between storm 1 and 2 from my experience when upgrading is the handling of shuffleGrouping. In storm 1, it was "strict" shuffle grouping, meaning tuples were distributed evenly across worker, no matter where workers are located physically. With storm 2, when stor

Re: Apache Storm Java 11 ++ support

Hi Yoav, to the best of my knowledge, storm officially only supports Java 8. I had recently tried to make it work on Java 14+, but that required some manual adaptions to the shaded deps package and also most likely broke compatibility with some libraries used for hadoop support (which we don't use

Re: Various configuration issues setting up a new cluster

. Nice weekend everyone Jonas Am Mi., 25. Nov. 2020 um 12:03 Uhr schrieb Jonas Krauss : > After doing more testing and finding the nimbus logfile in the storm dir, > I was able to narrow down the problem to a bug in Zookeeper 3.4, which is > somehow still used by storm internally, an

Re: Various configuration issues setting up a new cluster

devs thinks it's worth raising an issue I am glad to contribute, if I can. Thanks Jonas Am Di., 24. Nov. 2020 um 17:34 Uhr schrieb Jonas Krauss : > Hi all, > > we have recently tried to update zookeeper from 3.4.13 to 3.6.2 on our > production storm cluster without success. Ther

Various configuration issues setting up a new cluster

Hi all, we have recently tried to update zookeeper from 3.4.13 to 3.6.2 on our production storm cluster without success. Therefore, we are now tinkering with a test cluster, including just two nodes. The two nodes have the following setup: *OS* Ubuntu 20.04.1 LTS *Zookeeper *3.6.2 *Storm *2.2.0

Re: Passing worker JVM options not working as expected

18:42 Uhr schrieb Rui Abreu : > Hello Jonas, > > It should be using the *worker.childopts *defined > in storm/conf/storm.yaml. > > On Wed, 18 Nov 2020 at 16:04, Jonas Krauss wrote: > >> Hi all, >> >> we are running Storm 2.2.0 on openjdk build >>

Passing worker JVM options not working as expected

Hi all, we are running Storm 2.2.0 on openjdk build 1.8.0_272-8u272-b10-0+deb9u1-b10 in a cluster with five supervisors. We are trying to set individual worker child options for a topology via the Java Config object like so: Config conf = new Config(); conf.put(Config.WORKER_CHILDOPTS, "-Xmx%HEAP

HTML entities in storm's log viewer in browser

Hi all, I am trying to figure where the logviewer settings can be changed, as currently, the logviewer converts all non-ascii characters to HTML entities it seems. E.g. " becomes " which makes the logs quite hard to read. I have checked the raw log files on the server, these contain unescaped str

Storm UI Assigned Mem

Hi all, we are currently using storm 1.2.2 together with zookeeper 3.4.11. The value for assigned mem per topology in the storm ui under topology summary always displays 65, even though we assign xmx4096m by default through the storm.yaml. The workers are correctly started with -xmx4096m though.