as a MIT
> License) ?
>
> Alex
>
> Le lun. 13 mai 2024 à 11:51, Richard Zowalla a
> écrit :
> >
> > Hi all,
> >
> > REDIS switched it's license, which isn't compatible anymore [1]
> >
> > We have two options here (imho):
> >
>
Hi all,
REDIS switched it's license, which isn't compatible anymore [1]
We have two options here (imho):
(1) Drop the REDIS module
(2) Migrate to the OSS fork: https://github.com/valkey-io/valkey
WDYT?
Gruß
Richard
[1] https://redis.io/blog/redis-adopts-dual-source-available-licensing/
t; > > Kishor Patil
>> > >
>> > > > On Feb 28, 2024, at 4:37 PM, Bipin Prasad
>> > > >
>> > > wrote:
>> > > >
>> > > > +1
>> > > >On Wednesday, February 28, 2024 at 02:4
2024 at 13:20, Kishor Patil
>
> wrote:
>
> > +1
> >
> > Best regards,
> > Kishor Patil
> >
> > > On Feb 28, 2024, at 4:37 PM, Bipin Prasad
> > >
> > wrote:
> > >
> > > +1
> > > On Wedne
The Apache Storm community is pleased to announce the release of Apache
Storm version 2.6.2.
Apache Storm is a distributed, fault-tolerant, and high-performance
realtime computation system that provides strong guarantees on the
processing of data. You can read more about Apache Storm on the
Hi,
this vote passes with the following votes:
+1 Julien Nioche (binding)
+1 Alexandre Vermeerbergen (binding)
+1 Richard Zowalla (binding)
I'll proceed with the steps. Thx for your time!
Gruß
Richard
Here is my own +1 (binding)
Am Dienstag, dem 02.04.2024 um 10:32 +0200 schrieb Richard Zowalla:
> Hi all,
>
> I have posted a first release candidate for Apache Storm 2.6.2 and it
> is ready for testing.
>
> We upgraded libraries and pruned some dependencies which came
Hi all,
I have posted a first release candidate for Apache Storm 2.6.2 and it
is ready for testing.
We upgraded libraries and pruned some dependencies which came in as
transient dependencies.
Full list of changes in this release:
Hi,
any objections in doing a 2.6.2 after eastern?
We have some CVE fixes, so might be worth making a small update?
WDYT?
Best
Richard
+1
Am Mittwoch, dem 28.02.2024 um 09:08 + schrieb Julien Nioche:
> Hi,
>
> Following the discussion initiated by Richard [1], please vote on
> moving
> Storm from JIRA to GitHub issues
>
> The vote is open for at least the next 72 hours or as long as needed.
>
> [ ] +1 Move Storm from JIRA
Any additional thoughts?
Am Donnerstag, dem 22.02.2024 um 12:21 +0100 schrieb Alexandre
Vermeerbergen:
> +1 I agree that JIRA is overkill for the simple needs of incidents /
> enhancements tracking of Apache Storm
>
> Alexandre
>
> Le jeu. 22 févr. 2024 à 12:18, Richard
Hi all,
The ASF JIRA instance no longer allows users to self-sign-up (though it
DOES allow us to invite others). This is largely due to spam.
Most developers have a GitHub account (and that is where most folks
interact with Storm's code base), and this would meet folks where they
are, as opposed
The Apache Storm community is pleased to announce the release of Apache
Storm version 2.6.1.
Apache Storm is a distributed, fault-tolerant, and high-performance
realtime computation system that provides strong guarantees on the
processing of data. You can read more about Apache Storm on the
Hi all,
this vote passes with the following +1 being cast:
Julien Nioche (binding)
Alexandre Vermeerbergen (binding)
Richard Zowalla (binding)
Thanks to all voters. I'll proceed with the steps.
Gruß
Richard
Here is my own +1 (binding)
Am Dienstag, dem 30.01.2024 um 09:42 +0100 schrieb Richard Zowalla:
> Hi ladies & lords,
>
> I have posted a first release candidate for Apache Storm 2.6.1
> release
> and it is ready for testing.
>
> We fixed a few bugs and upgraded
Any more votes?
Am Dienstag, dem 30.01.2024 um 09:42 +0100 schrieb Richard Zowalla:
> Hi ladies & lords,
>
> I have posted a first release candidate for Apache Storm 2.6.1
> release
> and it is ready for testing.
>
> We fixed a few bugs and upgraded libraries.
ial..)
>
> Alexandre
>
> Le mar. 30 janv. 2024 à 14:12, Richard Zowalla
> a écrit :
> >
> > Here is the missing link. It is located at the usual location:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/
> >
> > Thx
Binary Release with sha512 signature
> files" is missing, can you please re-send the vote mail ?
>
> Thanks,
> Alexandre
>
> Le mar. 30 janv. 2024 à 09:42, Richard Zowalla a
> écrit :
> >
> > Hi ladies & lords,
> >
> > I have posted a first rele
Hi ladies & lords,
I have posted a first release candidate for Apache Storm 2.6.1 release
and it is ready for testing.
We fixed a few bugs and upgraded libraries.
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
Vermeerbergen:
> Hello Richard,
>
> +1, you must read my mind :)
>
> I am especially interest to get
> https://issues.apache.org/jira/browse/STORM-4025 backported to 2.6.1
> ;
> and your recent dependency update won Kryo, please.
>
> Kind regards,
> ALexandre
>
>
Hi all,
we had some fixes and dependency updates in Storm since our last
release.
Any objections in going for a 2.6.1 soon? Any lib upgrades we need to
include prior?
Did someone test our nightlies already?
Gruß
Richard
signature.asc
Description: This is a digitally signed message part
.org/thread/34kkzbcfr4qxcxmclgqmjc08o9s28gjz
> >
> > Gruß
> > Richard
> >
> >
> > Am 9. Januar 2024 11:33:48 MEZ schrieb Elisey Zanko
> > :
> > > Hi Richard,
> > >
> > > Sounds good to me.
> > > Where do I send the signed
and with what subject?
>
>Thanks,
>Elisey
>
>> On 9 Jan 2024, at 15:20, Richard Zowalla wrote:
>>
>> Hi all,
>>
>> just got a response from the incubator.
>>
>> What we would need from you (@Elisey) is a signed Software License
>> Grant (SGA)
f you feel, that this would work for you.
Gruß & thx
Richard
[1] https://www.apache.org/licenses/contributor-agreements.html#grants
[2] https://www.apache.org/licenses/software-grant-template.pdf
Am Dienstag, dem 09.01.2024 um 09:11 +0100 schrieb Richard Zowalla:
> Hi all,
>
> great news. I
Hi all,
great news. I reached out to the ASF incubator people to check, which
guidelines we need to follow in order to integrate / migrate ownership
of the code (repository) to the Storm project. Let's see what they say
would be the best strategy (even if it is just fork and re-license) and
if a
Hi all,
great news. I reached out to the ASF incubator people to check, which
guidelines we need to follow in order to integrate / migrate ownership
of the code (repository) to the Storm project. Let's see what they say
would be the best strategy (even if it is just fork and re-license) and
if a
+1 (think it would be good to "officially" be responsible and
distribute those on our own instead of relying on 3rd party repos)
Am Montag, dem 11.12.2023 um 14:57 + schrieb Julien Nioche:
> Dear Storm community,
>
> There was a recent discussion on the dev list [1] about a roadmap for
> the
It might be possible to build an abstraction layer + java 21-based
module, so ppl can decide (for ex by configuration) to switch to it or
not. If you do not activley decide to use it, it won't be a difference
to how it is currently working. Might need some carefully thinking and
some eyes on other
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/storm/
In addition, you can find recent SNAPSHOTs on the ASF SNAPSHOT
repository:
Hi folks,
this vote passes with 4 +1 from the following individuals:
- Julien Nioche (binding)
- Xin Wang (binding)
- Richard Zowalla (binding)
- Alexandre Vermeerbergen (binding)
I'll proceed with the steps. Thanks to all voters!
Richard
Here is my own +1
Am Donnerstag, dem 16.11.2023 um 10:19 +0100 schrieb Richard Zowalla:
> Hi folks,
>
> I have posted a first release candidate for the Apache Storm 2.6.0
> release and it is ready for testing.
>
> We updated a lot of dependencies, fixes some bugs and remove
Any other votes? Maybe from the other people recently added to the PMC? :-)
Am 16. November 2023 10:19:36 MEZ schrieb Richard Zowalla :
>Hi folks,
>
>I have posted a first release candidate for the Apache Storm 2.6.0
>release and it is ready for testing.
>
>We updated a lot of d
Hi folks,
I have posted a first release candidate for the Apache Storm 2.6.0
release and it is ready for testing.
We updated a lot of dependencies, fixes some bugs and removed some
/external modules. We are now also testing with Java 21, which looks
promising.
The Nexus staging repository is
2.6.0
> release ASAP !
>
> Note: I wish I had time to test all this with Java 21, but to be
> realistic I don't think it will happen before next month...
>
> Many thanks Richard for pushing us to try snapshot releases before
> entering a vote cycle!
>
> Alexandre
&
Thx. The related PR is merged.
Am Mittwoch, dem 15.11.2023 um 15:13 +0100 schrieb Richard Zowalla:
> Yes, feel free to provide a fix / pr + jira issue.
>
> It is just a matter of adding
>
>
> jakarta.xml.bind
> jakarta.xml.bind-api
>
>
va
> > EE
> > artefacts, a bunch of code migrated to Jakarta EE runs anway -
> > that's
> > what I like (smooth transitions)
> >
> > I update when I'll have results on my pre-production cluster at
> > scale
> > (max Thursday)
&
Hi all,
as written in the other thread, I have prepared another SNAPSHOT
artifact incorporting the feedbach received in the first round.
I would like to receive some feedback on the current SNAPSHOT build
again.
I just uploaded a 2.6.0-SNAPSHOT of Storm build from
13 nov. 2023 à 15:36, Julien Nioche
> a écrit :
> >
> > I agree with Richard. The next release contains enough big changes
> > and it
> > would be good to release it ASAP before embarking on another big
> > modification.
> >
> > Julien
> >
>
/lib-webapp/log4j-core-2.20.0.jar
>
> Disclaimer: I have no idea how hard this update would be.
>
> Anyone with good experience at updating SLF4J & related loggers could
> react on this proposal ?
>
> Thanks,
> Alexandre
>
>
> Le jeu. 9 nov. 2023 à
Ok, most of the stuff reported by grype should be fixed now.
I might be able to push a new snapshot within the next week, so we can
do some testing and than go for a release candiate / vote :)
Gruß
Richard
Am Donnerstag, dem 09.11.2023 um 08:53 +0100 schrieb Richard Zowalla:
> Maybe just
,
> Alexandre
>
> Le mar. 7 nov. 2023 à 17:43, Alexandre Vermeerbergen
> a écrit :
> >
> > Oh thank you very much for this cherry-pinking, I was too busy
> > doing
> > other unrelated stuff..
> >
> > Le mar. 7 nov. 2023 à 17:35, Richard Zowalla a
> &g
I cherry-picked your commit and put that on master
Am Dienstag, dem 07.11.2023 um 17:25 +0100 schrieb Richard Zowalla:
> You pushed on your own branch. You would need to push to apache/storm
> main branch or open a PR ;-)
>
> Am Samstag, dem 04.11.2023 um 10:36 +0100 schri
ght ?
> Note it's been running as is for long time and not breaking since
> many
> upgrades, of course it's not an excuse...
>
> I'll fix our code & continue checking if I see other impacts of 2.5.0
> -> 2.6.0 upgrade...
>
> Thanks,
> Alexandre
>
> Le sa
You pushed on your own branch. You would need to push to apache/storm
main branch or open a PR ;-)
Am Samstag, dem 04.11.2023 um 10:36 +0100 schrieb Alexandre
Vermeerbergen:
> Just did a 'git push' with that trivial fix... is that enough?
>
> Le sam. 4 nov. 2023 à 09:34, Richar
2023 à 08:53, Alexandre Vermeerbergen
> a écrit :
>>
>> Can you keep using my
>> 'STORM-3958-Capacity-to-set-Storm-UI's-title-in-conf/storm.yaml'
>> branch to push this fix, or should I create a new one?
>>
>> Le sam. 4 nov. 2023 à 08:14, Richard Zowalla a écr
n this are very simple: let me fix my own old code, after
>> > all this was impacting only one of my topologies, the other one were
>> > using more careful Integer.parseInt or Integer.parseLong to avoid
>> > making assumption on the way the values in th
f prepare() method?
> >
> > Also worth noting: "MyKOBolt" derives from BaseRichBolt , while
> > "MyOKBolt" derives from BaseBasicBolt => could this have any impact
> > on
> > this finding ?
> >
> > Last, I'm running this on Redhat Li
schrieb Richard Zowalla:
> Hi Alexandre,
>
> we are not in a hurry here :) - take as much as time you need.
>
> Gruß
> Richard
>
>
> Am Montag, dem 30.10.2023 um 07:50 +0100 schrieb Alexandre
> Vermeerbergen:
> > Hello Richard,
> >
> >
g the binary artifacts.
> Would it be OK if I can use up to end of this week so that I'll be
> able to have enough time to check all potential issues that this
> upgrade bring?
>
> Thanks,
> Alexandre
>
> Le lun. 30 oct. 2023 à 07:35, Richard Zowalla a
> écrit :
&g
Hi all,
before starting a release of 2.6.0-SNAPSHOT, I would like to receive
some feedback on the current SNAPSHOT build.
I just uploaded a 2.6.0-SNAPSHOT of Storm build from
https://github.com/apache/storm/commit/8f883086032669a8f04b09a3b312d60af5b44533
It is available via the ASF Snapshot
Hi,
we made a lot of improvements / dependency updates since our last
release?
Any objections for doing a new release?
Gruß
Richard
signature.asc
Description: This is a digitally signed message part
Hi all,
since our survey + vote included storm-sql and it remained untouched, I
am wondering if anyone can have a look at
https://github.com/apache/storm/pull/3509
It fails due to compile issues from calcite 1.16.0 to 1.32.0 and need
some adjustment.
Do we have any volunteers to give it a try?
Hi all,
this vote passes with the following +1
Alexandre Vermeerbergen (binding)
Julien Nioche (binding)
Richard Zowalla (binding)
I'll prepare a Jira + PR for the change.
Gruß
Richard
Am Donnerstag, dem 12.10.2023 um 10:59 +0200 schrieb Richard Zowalla:
> Hello all,
>
> This i
Here is my own +1
Am Donnerstag, dem 12.10.2023 um 10:59 +0200 schrieb Richard Zowalla:
> Hello all,
>
> This is the 2nd attempt due to an oversight in the components to be
> voted on.
>
> A few weeks ago we conducted a survey [1] and discussed the results
> [2]. Corres
Hello all,
This is the 2nd attempt due to an oversight in the components to be
voted on.
A few weeks ago we conducted a survey [1] and discussed the results
[2]. Corresponding details about the background can be found there. The
short version: We have too few resources to keep all modules up to
Due to an oversight on my side, I need to re-roll this vote.
"storm-jdbc" had enough votes to be still included. Will follow up
shortly.
signature.asc
Description: This is a digitally signed message part
12.10.2023 um 09:12 +0100 schrieb Edward Armes:
> -1 (non-binding)
> I would maybe think about keeping JDBC connector and dropping the
> Redis
> connector as the JDBC connector could potentially include Redis.
>
> Edward
>
> On Thu, 12 Oct 2023, 08:33 Richard Zowalla,
Hello all,
A few weeks ago we conducted a survey [1] and discussed the results
[2]. Corresponding details about the background can be found there. The
short version: We have too few resources to keep all modules up to
date. Old dependencies make it difficult to update the project.
Now it's time
ction on
> > the size of the code or number of dependencies to maintain is a
> > good thing.
> >
> > Julien
> >
> >
> >
> > On Mon, 2 Oct 2023 at 07:04, Richard Zowalla
> > wrote:
> >
> > > Hi all,
> > >
> > > our surv
Hi all,
our survey is closed and here are the results. We only have a sample
size of n=11, which isn't great but somehow represents the current
state of Storm (just revived from the Attic).
You find the results here: [1] (csv + image). User comments are also
added to the gist.
We had some
Hi,
yes, the coordinate move came with EE9, although EE8 will still be around some
day.
It will require to update Jetty _and_ check transient dependencies for
compatibility. I didn't check but it might be that some auth libs (from hadoop)
might rely on javax dependencies causing issues at
Just a last friendly reminder to participate! :)
Am Mittwoch, dem 30.08.2023 um 09:31 +0200 schrieb Richard Zowalla:
> Dear Apache Storm Users,
>
> we would like to update you on recent discussions regarding the
> future
> of the Apache Storm project and its modules. As y
Just another friendly reminder to participate! :)
Am Mittwoch, dem 30.08.2023 um 09:31 +0200 schrieb Richard Zowalla:
> Dear Apache Storm Users,
>
> we would like to update you on recent discussions regarding the
> future
> of the Apache Storm project and its modules. As y
Just a friendly reminder to participate! :)
Am Mittwoch, dem 30.08.2023 um 09:31 +0200 schrieb Richard Zowalla:
> Dear Apache Storm Users,
>
> we would like to update you on recent discussions regarding the
> future
> of the Apache Storm project and its modules. As y
I think you can fork the project, merge Bipin's changes and test with
Eclipse locally. If the changes solve the issues, it might be a good
thing otherwise we need to ensure, Eclipse users have a chance to be
onboarded :)
Am Dienstag, dem 29.08.2023 um 23:14 -0400 schrieb Alexandre
Vermeerbergen:
Dear Apache Storm Users,
we would like to update you on recent discussions regarding the future
of the Apache Storm project and its modules. As you may be aware, there
was a discussion to move Apache Storm to the attic due to resource
limitations and waning community involvement. However, we are
Hi all,
we (Julien, Alexandre and myself) have been discussing about the future
of the /external modules in Storm over in Slack (#Storm). As Slack
isn't the place for any decisions at the ASF, we are now moving these
discussion to the list.
Many of these modules aren't maintained anymore and
I am using IntelliJ, so no idea about Eclipse. Sorry.
Am Sonntag, dem 27.08.2023 um 21:21 -0400 schrieb Alexandre
Vermeerbergen:
> Hello,
>
> I am trying to use my Eclipse IDE to work on a contribution on storm
> project.
>
> I must be missing something, because I though I was just a matter of
It is a separate list usually to avoid too many mails on the actual dev list.
It is https://lists.apache.org/list.html?iss...@storm.apache.org issues@ for
Storm. Other ASF projects use commits@ etc.
Gruß
Richard
Am 21. August 2023 19:11:18 MESZ schrieb Alexandre Vermeerbergen
:
>Hello,
>
>I
ps://github.com/apache/storm-site/pull/45#pullrequestreview-1585813522
>?
>
>Thank,
>Alexandre
>
>Le dim. 20 août 2023 à 09:10, Richard Zowalla a écrit :
>>
>> Wait for reviews + 2-3 days before merging (timezones, holidays, etc), so
>> people have a chance to lo
k file to be part of the
>repository (it's a transient file generated by the bundle XXX command)
>
>Kind regards,
>Alexandre
>
>Le ven. 18 août 2023 à 22:00, Alexandre Vermeerbergen
> a écrit :
>>
>> OK, created https://issues.apache.org/jira/browse/STORM-3957 for
I am fine with it.
It might be a nice to have to track website changes in Jira, imho.
We won'T include such changes in a release's changelog but might be a
good thing to know, that someone is working on that task.
Gruß
Richard
Am Freitag, dem 18.08.2023 um 19:59 +0200 schrieb Alexandre
the
> title, initial content description, copy URL to initial JIRA, add
> attached materiel (if any) and copying related discussions will be an
> hassle...
>
> Thanks,
> Alexandre
>
> Le mer. 16 août 2023 à 09:24, Richard Zowalla a
> écrit :
> >
> > Hi all,
>
Hi all,
I'd like to take a moment to discuss something that I believe will
significantly enhance our project's collaboration and attract new
contributors: migrating from Jira to GitHub Issues and GitHub
Discussions.
We aren't using Jira very well in most cases, and the requirement for a
Jira
Gentle reminder: Please avoid cross posting. user@ is the perfect place for
your question.
Gruß
Richard
Am 8. August 2023 20:10:57 MESZ schrieb Prakash Choudhary
:
>Hello team,
>
>I am trying to run a Storm application and getting the below error I am new
>to Storm like to check if anyone got
" with my vote.
>
> Should I recast it, or I am right to wait for some formal annouce of
> my PMC
> status?
>
> Alexandre
>
>
>
> Le sam. 5 août 2023, 19:16, Richard Zowalla a
> écrit :
>
> > Hey Bipin,
> >
> > think it is sufficient, if
+1 (Binding - as before)
Am 5. August 2023 19:24:00 MESZ schrieb Bipin Prasad :
>Note: In order to be compliant with ASF procedures, we need an additional
>vote for Storm 2.5.0 RC4 (which was released yesterday) . Please test the
>following and vote:
>
>Storm Release candidate version 2.5.0 rc4
gt;
>On 2023/08/04 20:05:35 Richard Zowalla wrote:
>> Hi all,
>>
>>
>> During the last release vote, I noticed the following things that we
>> should do better next time to adhere to the ASF release guidelines
>> [1,2,3]:
>>
>> - We need at l
:15 Bipin Prasad wrote:
>> > Thank you for checking on this RC4 and the vote. I will add note about
>> > python3 in the README.
>> >
>> > On 2023/08/04 08:58:12 Richard Zowalla wrote:
>> > > Hi,
>> > >
>> > > 1. Checked SHA512 sum
Hi all,
During the last release vote, I noticed the following things that we
should do better next time to adhere to the ASF release guidelines
[1,2,3]:
- We need at least 3 (binding) votes for a release. A binding vote
originates from PMC members only (although community is encouraged to
also
Hi,
1. Checked SHA512 sums: OK
2. Checked ASC signatures: OK
3. Build from sources with the following setup
Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
Maven home: /usr/share/maven
Java version: 11.0.20, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-
openjdk-amd64
Default
I can confirm Julien's finding.
The /public folder is indeed missing from the tar.gz and zip file.
Gruß
Richard
Am Donnerstag, dem 03.08.2023 um 15:04 +0100 schrieb Julien Nioche:
> Thanks Bipin
>
> The source code in RC3 can now be compiled
> The signatures look OK
> I was able to run a
Hi,
can you close the staging repo on Nexus? Otherwise using the maven
artifacts won't be possible.
@all: Here is the repo for conviniance:
storm-2.5.0-rc3-test
Testing Storm 2.5.0 RC3
https://repository.apache.org/content/repositories/orgapachestorm-1108
I will test once the repository
On a clean, vanilla system without a custom maven mirror in place, I am
hitting the same issue.
The problem is, that Hive 2.3.9 declares the conjars.org repo:
https://github.com/apache/hive/blob/rel/release-2.3.9/pom.xml#L225
This is the reason imho, why it gets pulled into our Maven build.
Yup. This is snakeyaml 2.0 related.
@Julien: We had a similar issue in SC with version range syntax and snakeyaml
:-)
Gruß
Richard
Am 27. Juli 2023 16:13:30 MESZ schrieb Bipin Prasad :
>This appears to be the change in signature in snakeyaml 2.0 (which is used via
>transitive dependency in
The PR by Bipin seems to fix it? ;)
Am Freitag, dem 16.06.2023 um 20:19 +0200 schrieb Richard Zowalla:
> Ok from looking into gitact-script.sh, it looks like we are skipping
> storm-cassandra, storm-hive, storm-hdfs, storm-hbase, storm-sql,
> storm-
> hdfs-blobstore if we are buildi
+1
>
> Le lun. 12 juin 2023 à 11:57, Richard Zowalla a
> écrit :
> >
> > Some weeks passed, any updates?
> >
> > Gruß
> > Richard
> >
> > Am Donnerstag, dem 11.05.2023 um 19:16 -0400 schrieb P. Taylor
> > Goetz:
> > > Thanks fo
ule fails tests probably OOM - ASF JIRA
>
>
> |
>
> |
>
> |
>
>
>
>
> On Friday, June 16, 2023 at 09:58:32 AM PDT, Richard Zowalla
> wrote:
>
> Hi,
>
> looks like it only falls occasionally in Java 8 with an OOM issue /
> JVM crash. Might be possible to just incre
Hi,
looks like it only falls occasionally in Java 8 with an OOM issue / JVM crash.
Might be possible to just increase the JVM memory for that module.
I remember from the Travis migration, that we had some heap adjustments in the
scripts. Wdyt?
Gruß
Richard
Am 16. Juni 2023 17:57:21 MESZ
r
>
> > On May 11, 2023, at 8:39 AM, Richard Zowalla
> > wrote:
> >
> > Hello,
> >
> > I know we are all busy with our day jobs, but is there any news?
> >
> > We had some activity after a move to the attic was proposed. In the
> > proce
Hi,
https://github.com/apache/storm/commit/4fb1feb9466ec84ec7d2b9ac00c10e1bc9d60333
Should be already fixed but awaits a release.
Gruß
Richard
Am 12. Mai 2023 14:57:23 MESZ schrieb Alexandre Vermeerbergen
:
>Hello,
>
>I just created https://issues.apache.org/jira/browse/STORM-3918
>Any
> more than just 2 shoulders.
> >
> > Don't take it as a rant, it's just my opinion as someone who runs a
> > Storm Cluster in production and would love to help the project to
> > sustain.
> >
> > Gruß
> > Richard
> >
> > On 2023/05/02 12:58:00 Ri
timely releases again and the work regarding
maintenance is distributed on more than just 2 shoulders.
Don't take it as a rant, it's just my opinion as someone who runs a Storm
Cluster in production and would love to help the project to sustain.
Gruß
Richard
On 2023/05/02 12:58:00 Richard Zowalla
Any updates? :-)
Think Storm would benefit from a new release soon...
Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor Goetz:
> Quick update:
>
> The ASF Board voted to accept both our report and the resolution to
> change PMC Chair. Board feedback on our report was positive.
>
>
Hi Taylor,
as written in the other thread, I am happy to help.
If needed, I can also work on doing the mechanical work of a release
(already knowing the quirks with asf infrastructure).
Gruß
Richard
Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor Goetz:
> Quick update:
>
> The
; u...@storm.apache.org> wrote:
> > > > Ah Yea, also not opposed to the move to the attic if it's
> > > > determined to be most appropriate, but I had a similar
> > > > experience as Richard where I submitted some PRs, asked for
> > > > comments/t
A vote to move to the attic would not mean the end of
> Storm, the project can be forked by anyone who wants to continue the
> work
> (just as it can be forked today), it would just be outside of the
> ASF.
>
> On Thu, Jan 26, 2023 at 3:12 AM Richard Zowalla
> wrote:
>
A vote to move to the attic would not mean the end of
> Storm, the project can be forked by anyone who wants to continue the
> work
> (just as it can be forked today), it would just be outside of the
> ASF.
>
> On Thu, Jan 26, 2023 at 3:12 AM Richard Zowalla
> wrote:
>
Hi all,
I also experienced, that dev@ activity is quite low. I did provide some
PRs and asked questions a few months ago and didn't get any feedback,
although the PRs got merged in the end. I think, that we need some sort
of community rebuilding / revival, if we want to maintain Storm in a
Hi all,
I would like to ask kindly if we can get a 2.4.0 version soon?
It contains a zookeeper upgrade, which is required to fix an issue in
java 17 environments. Also it contains an upgraded log4j2 version,
which mitigates log4shell cve - I think it would be appreciated by the
community to have
1 - 100 of 106 matches
Mail list logo
