Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

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 for the hint! Am Dienstag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre Vermeerbergen: > Hi Richard, > > The link to "Storm Source and Binary Release with

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

Hi Richard, The link to "Storm Source and 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 release candidate for Apache

[VOTE] Release Apache Storm 2.6.1 (RC1)

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

Re: Storm 2.6.1 ?

I also updated my preproduction 10+ topologies with Storm snapshot generated 20240128 => everything runs fine and I confirm STORM-4025 is fixed ! Alex Le lun. 29 janv. 2024 à 14:37, Julien Nioche a écrit : > > Hi, > > Ran a StormCrawler toplogy with a nightly - looking good, no issues found >

Re: Storm 2.6.1 ?

Hi, Ran a StormCrawler toplogy with a nightly - looking good, no issues found Can't see any outstanding PRs to merge in the short term so would +1 to releasing what we currently have as 2.6.1 Thanks Julien On Fri, 26 Jan 2024 at 11:59, Julien Nioche wrote: > +1 to a 2.6.1 release > > The

Re: Community over Code EU 2024 Travel Assistance Applications now open!

Hi Julien, It's very nice that your submitted a Sorm-related topic for this conference, I wish your proposal to be accepted ! Unfortunately I won't be able to travel at that time, I hope to see you in broadcasts or records of your future session (betting it'll be accepted :) Alex Le sam. 27

Community over Code EU 2024 Travel Assistance Applications now open!

Dear Apache Storm community Below is a message from the Travel Assistance Committee (TAC) to announce that travel assistance applications for Community over Code EU 2024 are now open! I will be at the conference if my presentation on StormCrawler and Apache Storm is accepted. Anyone using or

STORM-4021: Add worker hooks via storm.yaml configuration file

Why can't I add worker hooks via the storm.yaml configuration file? Is it going to affect performance? Any difference between adding a worker hook for a topology vs in configuration file? If any?

Re: Storm 2.6.1 ?

+1 to a 2.6.1 release The nightlies are at https://nightlies.apache.org/storm/ A couple of changes were merged today, I'll try a nightly next week J On Fri, 26 Jan 2024 at 07:40, Richard Zowalla wrote: > Hi all, > > we had some fixes and dependency updates in Storm since our last > release. >

Re: [PR] STORM-4028 - Curator 5.6.0 (storm)

rzo1 merged PR #3624: URL: https://github.com/apache/storm/pull/3624 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: [PR] STORM-4027 - Kryo 5.6.0 (storm)

rzo1 merged PR #3623: URL: https://github.com/apache/storm/pull/3623 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: [PR] STORM-4026 - Thrift 0.19.0 (storm)

rzo1 merged PR #3622: URL: https://github.com/apache/storm/pull/3622 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: Storm 2.6.1 ?

I have no objection for such Storm 2.7.0 to Storm 2.6.1 renaming ! (so then nightly build shall automatically lead to 2.6.1 one renaming is done ?) Le ven. 26 janv. 2024 à 09:50, Richard Zowalla a écrit : > > Hi Alexandre, > > I think, that we can rename the milestone/version from 2.7.0 to 2.6.1

Re: Storm 2.6.1 ?

Hi Alexandre, I think, that we can rename the milestone/version from 2.7.0 to 2.6.1 as we do not have any public facing breaking changes in the API (afaik). So instead of going 2.7.0, we can just do a 2.6.1 (imho). Gruß Richard Am Freitag, dem 26.01.2024 um 09:48 +0100 schrieb Alexandre

Re: Storm 2.6.1 ?

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 Le ven. 26 janv. 2024 à 08:40, Richard Zowalla a écrit : > > Hi all, >

[PR] STORM-4028 - Curator 5.6.0 (storm)

rzo1 opened a new pull request, #3624: URL: https://github.com/apache/storm/pull/3624 ## What is the purpose of the change [*(Explain why we should have this change)*](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314425=12353185) ## How was the change

[PR] STORM-4027 - Kryo 5.6.0 (storm)

rzo1 opened a new pull request, #3623: URL: https://github.com/apache/storm/pull/3623 ## What is the purpose of the change - https://github.com/EsotericSoftware/kryo/releases ## How was the change tested - CI -- This is an automated message from the Apache Git

Storm 2.6.1 ?

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

Re: [PR] STORM-4026 - Thrift 0.19.0 (storm)

rzo1 commented on PR #3622: URL: https://github.com/apache/storm/pull/3622#issuecomment-1910505380 Yeah, need to fix that license madness ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

[PR] STORM-4026 - Thrift 0.19.0 (storm)

rzo1 opened a new pull request, #3622: URL: https://github.com/apache/storm/pull/3622 ## What is the purpose of the change - Upgrades to Thrift 0.19.0 - Regenerate thrift code ## How was the change tested - CI -- This is an automated message from the Apache Git

Re: [PR] [STORM-3713] fix race-condition by applying submitLock to leaderCallBack (storm)

jnioche commented on PR #3353: URL: https://github.com/apache/storm/pull/3353#issuecomment-1910015477 thanks @RuiLi8080, sorry it took so long but the project is now a bit more active thanks largely to @rzo1 -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] [STORM-3713] fix race-condition by applying submitLock to leaderCallBack (storm)

jnioche merged PR #3353: URL: https://github.com/apache/storm/pull/3353 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] fix flaky tests testTopologyIsolation and testDefaultResourceAwareStrategySharedMemory (storm)

rzo1 commented on PR #3603: URL: https://github.com/apache/storm/pull/3603#issuecomment-1909968017 Got no response of the opener, no flaky tests observed in the last months / weeks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] fix flaky tests testTopologyIsolation and testDefaultResourceAwareStrategySharedMemory (storm)

rzo1 closed pull request #3603: fix flaky tests testTopologyIsolation and testDefaultResourceAwareStrategySharedMemory URL: https://github.com/apache/storm/pull/3603 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [PR] STORM-4025 - ClassCastException when changing log level in Storm UI (storm)

rzo1 merged PR #3621: URL: https://github.com/apache/storm/pull/3621 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: [PR] [STORM-4023] Background periodic Kerberos re-login should use same JAAS configuration as initial login (storm)

rzo1 merged PR #3619: URL: https://github.com/apache/storm/pull/3619 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: [PR] STORM-4024 Fix Bolt Input Stats are blank if topology.acker.executors… (storm)

rzo1 merged PR #3620: URL: https://github.com/apache/storm/pull/3620 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: [PR] STORM-4024 Fix Bolt Input Stats are blank if topology.acker.executors… (storm)

Scomocouk commented on PR #3620: URL: https://github.com/apache/storm/pull/3620#issuecomment-1908670566 **Additional Explanation** The 'id2procAvg' parameter of aggBoltStreamsLatAndCount method will always be null if topology.acker.executors is 0. In this scenario, the series of null

Re: [PR] Bump org.springframework:spring-core from 5.3.27 to 6.0.15 in /examples/storm-jms-examples (storm)

dependabot[bot] commented on PR #3618: URL: https://github.com/apache/storm/pull/3618#issuecomment-1908599008 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let

Re: [PR] Bump org.springframework:spring-core from 5.3.27 to 6.0.15 in /examples/storm-jms-examples (storm)

rzo1 closed pull request #3618: Bump org.springframework:spring-core from 5.3.27 to 6.0.15 in /examples/storm-jms-examples URL: https://github.com/apache/storm/pull/3618 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[PR] [STORM-4023] Background periodic Kerberos re-login should use same JAAS configuration as initial login (storm)

noslowerdna opened a new pull request, #3619: URL: https://github.com/apache/storm/pull/3619 ## What is the purpose of the change This change is needed to avoid having to specify `java.security.auth.login.config` as both a Storm configuration property (for initial login) and a Java

[PR] Bump org.springframework:spring-core from 5.3.27 to 6.0.15 in /examples/storm-jms-examples (storm)

dependabot[bot] opened a new pull request, #3618: URL: https://github.com/apache/storm/pull/3618 Bumps [org.springframework:spring-core](https://github.com/spring-projects/spring-framework) from 5.3.27 to 6.0.15. Release notes Sourced from

Re: get blob meta exception

These are EC2 instances? Or is Storm running in AWS EKS? Socket timeout is generally 60 seconds, but can you verify from your log timestamps to infer what your socket timeout might be. Sent from Yahoo Mail for iPhone On Friday, January 19, 2024, 12:45 PM, Devendar Rao wrote: The size of

Re: get blob meta exception

The size of the jar is 270M. We've 19 topologies each with 270M jar size. Yes, we use AWS EBS volumes for supervisors and Nimbus uses the local Nvme(instance store). Do you think increasing this topology.max.replication.wait.time.sec would help? On Fri, Jan 19, 2024 at 12:29 PM Bipin Prasad

Re: get blob meta exception

What is the size of the blob (the larger is probably the jar). The download time would depend on the network speed. Also noticed the name was f the mounted file system as ephemeral. These are not persistent storage? How about on the nimbus? Sent from Yahoo Mail for iPhone On Friday, January

Re: get blob meta exception

We also see these warnings during the issue. Are there any settings which controls the availability of these files. Is there a setting which controls the wokrer to to keep in wait till the required files are available? Do we need to increase the value for this setting -

Re: get blob meta exception

Hi Bipin, There are no disk space issues on the nimbus host. We also see this exception. I think this is the effect not the cause. Not completely sure though. 2024-01-18 11:47:16.018 o.a.s.t.ProcessFunction pool-29-thread-60 [ERROR] Internal error processing beginBlobDownload

get blob meta exception

Hi, We're constantly seeing issues in storm 2.3.0 with blobs with each topology deployment. Supervisor/nimbus dies after seeing the below exceptions. Is this a known issue? Are we hitting any blob cache size limits? Exceptions: "Could not download the blob with key:" o.a.s.d.n.Nimbus

Re: get blob meta exception

Hello Devender,   The zookeeper entry is expected to be removed when the topology is killed. It appears that you are using local file store blob. So the blobs are (expected to be) on the nimbus. Can you check the mailbox directory and confirm whether or not the blob for this topology made it

Re: get blob meta exception

Thanks Bipin for the response. To add more details: Whenever a new topology is deployed nimbus doesn't respond and supervisor(s) go down. We have to restart the services to bring the cluster back to normal. Another error we see: o.a.s.b.BlobStoreUtils BLOB-STORE-TIMER [ERROR] Could not download

Re: get blob meta exception

Full stack trace: 2024-01-18 18:27:12.889 o.a.s.d.n.Nimbus pool-29-thread-22 [WARN] get blob meta exception. org.apache.storm.utils.WrappedKeyNotFoundException: topology-A-7-1704896101-stormjar.jar at org.apache.storm.blobstore. LocalFsBlobStore.getStoredBlobMeta(LocalFsBlobStore.java:258)

Re: get blob meta exception

Can you post the full stack trace? I want to confirm that this is logged while trying to obtain the heartbeat.This message is a warning message and is not expected to shutdown nimbus. Sent from Yahoo Mail for iPhone On Thursday, January 18, 2024, 11:19 AM, Devendar Rao wrote: Hi, We're

get blob meta exception

Hi, We're constantly seeing issues in storm 2.3.0 with blobs with each topology deployment. Supervisor nodes die after seeing the below exceptions. Is this a known issue? Are we hitting any blob cache size limits? Exceptions: "Could not download the blob with key:" 2024-01-18 18:27:12.889

Docker images

Dear Storm community, You can now find version 2.6.0 of Apache Storm on Dockerhub , other versions have been deprecated. As you probably read in a separate thread, the code of the Docker images has been kindly donated by Elisey Zanko and is now at Apache. You can

Re: [PR] [STORM-4022] Do not log Exception when getting heartbeat timeout for dead topologies (storm)

jnioche merged PR #3617: URL: https://github.com/apache/storm/pull/3617 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] [STORM-4022] Do not log Exception when getting heartbeat timeout for dead topologies (storm)

bipinprasad opened a new pull request, #3617: URL: https://github.com/apache/storm/pull/3617 ## What is the purpose of the change *In AWS EKS environment, the nimbus log seems to be flooded with heartbeat time exception messages for dead topologies* ## How was the change

Re: [PR] STORM-4018 - Wrong order of the params in Storm API resource (storm)

jnioche merged PR #3616: URL: https://github.com/apache/storm/pull/3616 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

jnioche commented on PR #3615: URL: https://github.com/apache/storm/pull/3615#issuecomment-1892317878 Thanks @Scomocouk -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

jnioche merged PR #3615: URL: https://github.com/apache/storm/pull/3615 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: Contribute Docker images to Apache Storm?

Hi Richard, Sounds good to me. Where do I send the signed SGA 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)

Re: Contribute Docker images to Apache Storm?

Hi all, I’ve just signed and sent the SGA. Let me know if you wish to switch https://hub.docker.com/_/storm to your git repo. Here’s how it could look like: https://github.com/docker-library/official-images/pull/9319

Re: Contribute Docker images to Apache Storm?

Massive thank you to Elisey for donating the Docker image repo and having maintained it for so long. Thanks to Richard as well for making it happen On Wed, 10 Jan 2024 at 19:34, Richard Zowalla wrote: > Hi all, > > thanks Elisey for submitting the SGA. It was received. > > I just migrated the

Re: Contribute Docker images to Apache Storm?

Hi all, thanks Elisey for submitting the SGA. It was received. I just migrated the current code to https://github.com/apache/storm-docker and made some ASF specific updates after the code donation. I also opened a PR against the official images to transfer ownership

Re: Contribute Docker images to Apache Storm?

Hey Elisey, it is described here: https://www.apache.org/licenses/contributor-agreements.html#submitting It basically goes to secret...@apache.org Subject something like: "SGA for Storm Docker". In the mail just add the signed SGA (as described under the link), a link to the GitHub Repo (is

Re: Contribute Docker images to Apache Storm?

Hi all, just got a response from the incubator. What we would need from you (@Elisey) is a signed Software License Grant (SGA) [1] downloadable here [2]. It would need to follow the procedere described under "HOW-TO: SUBMITTING LICENSE AGREEMENTS AND GRANTS". Let us know, if you feel, that

Re: Contribute Docker images to Apache Storm?

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

Re: Contribute Docker images to Apache Storm?

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

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

Scomocouk commented on PR #3615: URL: https://github.com/apache/storm/pull/3615#issuecomment-1881677336 As suggested from my previous pull request (https://github.com/apache/storm/pull/3614), I have resubmitted this for merging into master instead of 2.4.x-branch -- This is an automated

[PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

Scomocouk opened a new pull request, #3615: URL: https://github.com/apache/storm/pull/3615 ## What is the purpose of the change Fixes STORM-4017 I raised recently so that isAnyWindowsProcessAlive works correctly in Windows. What prompted this was that we are evaluating Storm 2.5.0

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

Scomocouk closed pull request #3614: STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids URL: https://github.com/apache/storm/pull/3614 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

rzo1 commented on PR #3614: URL: https://github.com/apache/storm/pull/3614#issuecomment-1881242017 Therefore, I suggest to target `main` with the change and post a related mail on dev@ -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

rzo1 commented on PR #3614: URL: https://github.com/apache/storm/pull/3614#issuecomment-1881216003 Thanks for the PR. I definitley see it in the next release of Storm. However, given the limited amount of volunteers working on Storm (it was discussed to move it to the attic a couple of

Re: [PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

Scomocouk commented on PR #3614: URL: https://github.com/apache/storm/pull/3614#issuecomment-1881120469 This request is to merge to 2.4.x-branch. However, we are actaully working with 2.5.0 but notice there is no corresponding 2.5.x-branch to merge in to. Can this be added? (We are working

[PR] STORM-4017 Fix for isAnyWindowsProcessAlive with multiple pids (storm)

Scomocouk opened a new pull request, #3614: URL: https://github.com/apache/storm/pull/3614 ## What is the purpose of the change Fixes STORM-4017 I raised recently so that isAnyWindowsProcessAlive works correctly in Windows. What prompted this was that we are evaluating Storm 2.5.0

Re: Contribute Docker images to Apache Storm?

Hi Elisey, Thanks for your email and great to hear that you'd be happy to contribute the code. I am CCing the Storm dev list so that our discussion is in the open and members of the community can contribute to it. For the people on dev@, Elisey is the author of the Storm images on Docker

Re: [PR] [STORM-4015][DOCS] Update the minimum Java version required to Java 11 (storm)

rzo1 commented on PR #3613: URL: https://github.com/apache/storm/pull/3613#issuecomment-1877352598 Website is updated. Couldn't find you in the ASF Jira. Feel free to leave a comment in https://issues.apache.org/jira/browse/STORM-4015 and I will assign it to you later. Thanks for

Re: [PR] [STORM-4015][DOCS] Update the minimum Java version required to Java 11 (storm)

engrravijain commented on PR #3613: URL: https://github.com/apache/storm/pull/3613#issuecomment-1877183419 Welcome @rzo1! :) Yes, I have a jira account with username **engrravijain** -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [PR] [STORM-4015][DOCS] Update the minimum Java version required to Java 11 (storm)

rzo1 commented on PR #3613: URL: https://github.com/apache/storm/pull/3613#issuecomment-1877179116 Thanks @engrravijain - will re-generate the website + close the Jira afterwards. If you have a Jira account, plz let me know, so I can assign the issue accordingly ;-) -- This is an

Re: [PR] [STORM-4015][DOCS] Update the minimum Java version required to Java 11 (storm)

jnioche merged PR #3613: URL: https://github.com/apache/storm/pull/3613 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] [STORM-4015][DOCS] Update the minimum Java version required to Java 11 (storm)

engrravijain commented on PR #3613: URL: https://github.com/apache/storm/pull/3613#issuecomment-1877111485 @rzo1 please review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

[PR] [STORM-4015][DOCS] Update the minimum Java version required to Java 11 (storm)

engrravijain opened a new pull request, #3613: URL: https://github.com/apache/storm/pull/3613 ## What is the purpose of the change Update the documentation to reflect the minimum version of Java required. *(Explain why we should have this change)* Updated documentation

Meet our keynote speakers and register to Community Over Code EU!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] * Merge with the ASF EUniverse!The registration for

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

rzo1 commented on PR #3612: URL: https://github.com/apache/storm/pull/3612#issuecomment-1866000242 @reiabreu Great. Don't forget to assign the jira to you + set the fix version and close it :) -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

reiabreu merged PR #3612: URL: https://github.com/apache/storm/pull/3612 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

reiabreu commented on PR #3612: URL: https://github.com/apache/storm/pull/3612#issuecomment-1865996752 @rzo1 Cheers for that, the linking process was incomplete, I have solved that now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

rzo1 commented on PR #3612: URL: https://github.com/apache/storm/pull/3612#issuecomment-1865965588 @reiabreu You just need to link your ASF ID with GitHub via https://gitbox.apache.org/boxer/ (than it will automatically provide your GitHub account with the required permissions) -- This

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

reiabreu commented on PR #3612: URL: https://github.com/apache/storm/pull/3612#issuecomment-1865962703 @rzo1 I'm afraid I don't have write permissions -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

rzo1 commented on PR #3612: URL: https://github.com/apache/storm/pull/3612#issuecomment-1865695510 @reiabreu feel free to merge it yourself ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) (storm)

reiabreu closed pull request #3611: [STORM-4016] KafkaSpout: moving to poll(Duration) due to deprecation of poll(long) URL: https://github.com/apache/storm/pull/3611 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [VOTE] Docker images for Apache Storm

Hi, The vote passes with 4 +1 (Richard, Bipin, Xin, myself) 1 +0 (Alexandre) I'll go ahead and ask infra to set us up. Thanks Julien On Wed, 13 Dec 2023 at 15:37, Julien Nioche wrote: > Forgot to add my own +1 > > On Mon, 11 Dec 2023 at 14:58, Julien Nioche wrote: > >> Dear Storm

Re: [VOTE] Docker images for Apache Storm

Forgot to add my own +1 On Mon, 11 Dec 2023 at 14:58, Julien Nioche wrote: > Dear Storm community, > > There was a recent discussion on the dev list [1] about a roadmap for the > next release (major or minor). One of the items was to release Docker > images for Apache Storm ourselves. There are

Re: [VOTE] Docker images for Apache Storm

+1 Bipin Prasad 于2023年12月12日 周二21:26写道： > [+1] for publishing Storm docker images as part of Storm project > > > Sent from Yahoo Mail for iPhone > > > On Tuesday, December 12, 2023, 1:18 AM, Julien Nioche < > lists.digitalpeb...@gmail.com> wrote: > > [0] is of course a valid option, just like in

Re: [VOTE] Docker images for Apache Storm

[+1] for publishing Storm docker images as part of Storm project  Sent from Yahoo Mail for iPhone On Tuesday, December 12, 2023, 1:18 AM, Julien Nioche wrote: [0] is of course a valid option, just like in any vote in any ASF-related project Thanks On Tue, 12 Dec 2023 at 09:01, Alexandre

Re: [VOTE] Docker images for Apache Storm

[0] is of course a valid option, just like in any vote in any ASF-related project Thanks On Tue, 12 Dec 2023 at 09:01, Alexandre Vermeerbergen < avermeerber...@gmail.com> wrote: > Hello, > > I would have voted [0] if possible, but only [+1] or [-1] are proposed ;) > > Indeed, regarding Docker

Re: [VOTE] Docker images for Apache Storm

Hello, I would have voted [0] if possible, but only [+1] or [-1] are proposed ;) Indeed, regarding Docker images, I tend to be reluctant to use community images appart from OS base ones and built mine based on my actual needs which are: 1. To use a specific JVM (I'm more found of OpenJ9 - aka

Re: [VOTE] Docker images for Apache Storm

+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

[VOTE] Docker images for Apache Storm

Dear Storm community, There was a recent discussion on the dev list [1] about a roadmap for the next release (major or minor). One of the items was to release Docker images for Apache Storm ourselves. There are Docker images but maintained by a third party [2]. By managing the images ourselves,

Re: Roadmap Apache Storm 3.x

Let's find something to break then... or just have another 2.x On Fri, 8 Dec 2023 at 07:26, Alexandre Vermeerbergen < avermeerber...@gmail.com> wrote: > Hello Julien, > > Sorry for asking so late, but one detail puzzles my in this > discussion: according to semantic versioning, the change of

Re: Roadmap Apache Storm 3.x

Hello Julien, Sorry for asking so late, but one detail puzzles my in this discussion: according to semantic versioning, the change of major version number is meant to introduce changes breaking compatibility. Unless I have missed something, I do not see any changes that would break compatibility

Re: [PR] STORM-4009 - Regenerate using thrift 0.18.1 (storm)

rzo1 merged PR #3608: URL: https://github.com/apache/storm/pull/3608 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: Roadmap Apache Storm 3.x

I agree on the need to fix logviewer functionality so that it works in a Kubernetes deployment (eg AWS EKS or GKE). Sent from Yahoo Mail for iPhone On Thursday, December 7, 2023, 4:26 AM, Richard Zowalla wrote: It might be possible to build an abstraction layer + java 21-based module, so

Re: Roadmap Apache Storm 3.x

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

Re: Roadmap Apache Storm 3.x

Agreed for leaving fiber projet aside from 3.x Re-logviewer : how about my idea to use storm-ui's app server and write some kind of proxy servlet to make all traffic related to logs retrieval going to storm UI ? Le jeu. 7 déc. 2023 à 13:06, Julien Nioche a écrit : > > Thanks Alexandre, > > I

Re: Roadmap Apache Storm 3.x

Thanks Alexandre, I haven't looked nor know anything about fibers but it sounds promising. Forcing Java 21 would be problematic I think. Given that it is a fundamental change, maybe this could live in a separate branch until thoroughly tested and Java 21 is the norm. What do you think?

Re: Roadmap Apache Storm 3.x

Hello Julien, Excellent initiative indeed ! I am very fond of "Find a way of having the Logviewer work in Docker" topic, because I think it's similar to a shorter time need which I have when deploying AWS EC2 with a VPN to avoid exposure of "internal VMs" : in this case, the public FQDN of

Roadmap Apache Storm 3.x

Hi, Now that Storm is active again and we are getting regular releases, should we try to come up with a roadmap for the Storm 3.x? Here are a few things that come to mind - Finish the migration from Clojure to Java (it is still used in the tests I think) - Find a way of having the

Re: [PR] STORM-4011 - Migrate Storm itself to use Commons Collections 4 (storm)

rzo1 merged PR #3610: URL: https://github.com/apache/storm/pull/3610 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

Re: [PR] STORM-4010 - Reduce ASM Mess in dependency tree (storm)

rzo1 merged PR #3609: URL: https://github.com/apache/storm/pull/3609 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

[PR] STORM-4011 - Migrate Storm itself to use Commons Collections 4 (storm)

rzo1 opened a new pull request, #3610: URL: https://github.com/apache/storm/pull/3610 ## What is the purpose of the change - Migrate to commons collections 4 inside storm. ## How was the change tested - CI -- This is an automated message from the Apache Git Service.

[PR] STORM-4009 - Regenerate using thrift 0.18.1 (storm)

rzo1 opened a new pull request, #3608: URL: https://github.com/apache/storm/pull/3608 ## What is the purpose of the change - Regenerate old thrift code with new thrift compiler for the sake of newer language features. ## How was the change tested - CI -- This is an

<    1   2   3   4   5   6   7   8   9   10   >