Hi all, I'm running unit tests for Hadoop 2.8.5. I had a script that basically repeatedly run command mvn -Dtest=t1,t2,t3,... test with different test selections. And after each test command finishes, I need to get test running stats for other purposes.
The problem is that I saw lingering java processes running surefirebooterxxxxx.jar that consumes a lot of memory and CPU resources. Is this owing to setting <forkedProcessTimeoutInSeconds> to a timeout value under maven-surefire-plugin configuration (in hadoop-project/pom.xml)? If so, I'm wondering if there are specific reasons (e.g. required by certain unit tests) for using a timeout value and delay the killing of forked JVMs, instead of doing something like <shutdown>exit</shutdown>? I changed my pom configuration to just using shutdown exit and I didn't see lingering java surefirebooter processes anymore, but I'm not sure if this change would break any Hadoop unit test. Any thoughts on this? Thanks a lot in advance. Best, Elaine
