[STORM-3792] Change pom.xml to use more test JVM threads without reuse

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: blobstore, examples, integration-test, storm-hdfs, storm-hive, storm-kafka, storm-kafka-client, storm-kafka-monitor, storm-server, storm-sql
• Assignee: Bipin Prasad
• Reporter: Bipin Prasad
• Created: 24/Aug/21 19:46
• Updated: 16/Nov/23 08:15
• Resolved: 15/Aug/23 07:52

Description

Maven surefire plugin configuration has two important flags:

  (1) reuseForks - setting of true mean reuse created JVMs.

  (2) forkCount - number of JVMs to create for testing. Pure number is an absolute count, whereas 1.0C means same as the number of CPUs.

Reusing forked JVMs can cause somewhat indeterminate failures in test when global class instances are not properly initialized or cleaned. An example of such a singleton class Time. 

Not reusing will cause a slowdown in tests. 

To mitigate this slowdown, wherever the "forkCount=1", change it to "forkCount=1.0C" and add reuseForks=false if not already present. However, some modules (example storm-hdfs) forkCount cannot be increased from 1 to 1.0C, due to either resources limits or global locking (as in hdfs tests). 

Issue Links

• links to: Pull Request