Re: Storm Cassandra

2023-06-16 Thread 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 building with Java 11 and run them with Java
8. That explains why Java 11 runs do not fail ;-)

Nevertheless, we have runs, which are just working fine with Java 8. If
we fail, we fail (at the moment) on pull requests with a JVM crash, see
[1].

It seems, that we are already running with 3g memory, so it might not
be the root problem, but could be related (due to GH action limits /
overall consumption in the org).

On master, it seems to be fine (just happens on some PRs).

[1] https://gist.github.com/rzo1/5aa510022f27bdf3c8eda66089774b68


Am Freitag, dem 16.06.2023 um 17:25 + schrieb Bipin Prasad:
>  Created Jira [STORM-3923] Cassandra module fails tests probably OOM
> - ASF JIRA . I think mvn test is using 3gb (inherited from main
> pom.xml), but will add directly in its pom under Cassandra. Also
> MAVEN_OPTS in git actions is set to 1.5gb. I wonder if that is
> limiting the memory.
> 
> > 
> > 
> >  | 
> [STORM-3923] Cassandra module 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 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 schrieb Bipin Prasad
> :
> > All,
> >   I am working on creating a new release for Storm 2.5.0.
> > Unfortunately,
> > storm-cassandra has been failing tests since we moved to Git
> > Actions. Can
> > someone take a look at it and possibly get it to work - with a
> > newer
> > version of Cassandra if possible and/or upgraded tests?
> > 
> >   If no one is using Storm Cassandra (under xternal/storm-
> > cassandra), I
> > can exclude this from the build and release). Open to other
> > suggestions.
> > 
> > Thanks
> > --Bipin
>   



[GitHub] [storm] bipinprasad opened a new pull request, #3545: [STORM-3923] Increase MAVEN_OPTS max memory setting to 2gb

2023-06-16 Thread via GitHub


bipinprasad opened a new pull request, #3545:
URL: https://github.com/apache/storm/pull/3545

   ## What is the purpose of the change
   
   *Storm Cassandra (external/storm-cassandra) test fail because OOM*
   
   ## How was the code tested
   
   *Git Actions build and test run as part of this pull request*


-- 
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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: Storm Cassandra

2023-06-16 Thread Bipin Prasad
 Created Jira [STORM-3923] Cassandra module fails tests probably OOM - ASF JIRA 
. I think mvn test is using 3gb (inherited from main pom.xml), but will add 
directly in its pom under Cassandra. Also MAVEN_OPTS in git actions is set to 
1.5gb. I wonder if that is limiting the memory.

| 
| 
|  | 
[STORM-3923] Cassandra module 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 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 schrieb Bipin Prasad :
>All,
>  I am working on creating a new release for Storm 2.5.0. Unfortunately,
>storm-cassandra has been failing tests since we moved to Git Actions. Can
>someone take a look at it and possibly get it to work - with a newer
>version of Cassandra if possible and/or upgraded tests?
>
>  If no one is using Storm Cassandra (under xternal/storm-cassandra), I
>can exclude this from the build and release). Open to other suggestions.
>
>Thanks
>--Bipin
  

Re: Storm Cassandra

2023-06-16 Thread Richard Zowalla
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 schrieb Bipin Prasad :
>All,
>   I am working on creating a new release for Storm 2.5.0. Unfortunately,
>storm-cassandra has been failing tests since we moved to Git Actions. Can
>someone take a look at it and possibly get it to work - with a newer
>version of Cassandra if possible and/or upgraded tests?
>
>   If no one is using Storm Cassandra (under xternal/storm-cassandra), I
>can exclude this from the build and release). Open to other suggestions.
>
>Thanks
>--Bipin


Re: Storm Cassandra

2023-06-16 Thread Alexandre Vermeerbergen
+1 to exclude Storm Cassandra
(my 2 cents)

Thanks,
Alex

Le ven. 16 juin 2023 à 17:58, Bipin Prasad  a écrit :
>
> All,
>I am working on creating a new release for Storm 2.5.0. Unfortunately,
> storm-cassandra has been failing tests since we moved to Git Actions. Can
> someone take a look at it and possibly get it to work - with a newer
> version of Cassandra if possible and/or upgraded tests?
>
>If no one is using Storm Cassandra (under xternal/storm-cassandra), I
> can exclude this from the build and release). Open to other suggestions.
>
> Thanks
> --Bipin


Storm Cassandra

2023-06-16 Thread Bipin Prasad
All,
   I am working on creating a new release for Storm 2.5.0. Unfortunately,
storm-cassandra has been failing tests since we moved to Git Actions. Can
someone take a look at it and possibly get it to work - with a newer
version of Cassandra if possible and/or upgraded tests?

   If no one is using Storm Cassandra (under xternal/storm-cassandra), I
can exclude this from the build and release). Open to other suggestions.

Thanks
--Bipin


TAC Applications for Community Over Code North America and Asia now open

2023-06-16 Thread Gavin McDonald
Hi All,

(This email goes out to all our user and dev project mailing lists, so you
may receive this
email more than once.)

The Travel Assistance Committee has opened up applications to help get
people to the following events:


*Community Over Code Asia 2023 - *
*August 18th to August 20th in Beijing , China*

Applications for this event closes on the 6th July so time is short, please
apply as soon as possible. TAC is prioritising applications from the Asia
and Oceania regions.

More details on this event can be found at:
https://apachecon.com/acasia2023/

More information on how to apply please read: https://tac.apache.org/


*Community Over Code North America - *
*October 7th to October 10th in Halifax, Canada*

Applications for this event closes on the 22nd July. We expect many
applications so please do apply as soon as you can. TAC is prioritising
applications from the North and South America regions.

More details on this event can be found at: https://communityovercode.org/

More information on how to apply please read: https://tac.apache.org/


*Have you applied to be a Speaker?*

If you have applied or intend to apply as a Speaker at either of these
events, and think you
may require assistance for Travel and/or Accommodation - TAC advises that
you do not
wait until you have been notified of your speaker status and to apply
early. Should you
not be accepted as a speaker and still wish to attend you can amend you
application to
include Conference fees, or, you may withdraw your application.

The call for presentations for Halifax is here:
https://communityovercode.org/call-for-presentations/
and you have until the 13th of July to apply.

The call for presentations for Beijing is here:
https://apachecon.com/acasia2023/cfp.html
and you have until the 18th June to apply.

*IMPORTANT Note on Visas:*

It is important that you apply for a Visa as soon as possible - do not wait
until you know if you have been accepted for Travel Assistance or not, as
due to current wait times for Interviews in some Countries, waiting that
long may be too late, so please do apply for a Visa right away. Contact
tac-ap...@tac.apache.org if you need any more information or assistance in
this area.

*Spread the Word!!*

TAC encourages you to spread the word about Travel Assistance to get to
these events, so feel free to repost as you see fit on Social Media, at
work, schools, universities etc etc...

Thank You and hope to see you all soon

Gavin McDonald on behalf of the ASF Travel Assistance Committee.