wssmao opened a new issue, #7972: URL: https://github.com/apache/seatunnel/issues/7972
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened OOM appear, when I run st cluster after a long time . ### SeaTunnel Version 2.3.5 ### SeaTunnel Config ```conf # JVM Heap -Xms6g -Xmx6g # JVM Dump -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/seatunnel/dump/zeta-server # Metaspace -XX:MaxMetaspaceSize=6g # G1GC -XX:+UseG1GC ``` ### Running Command ```shell nohup ./bin/seatunnel.sh ``` ### Error Exception ```log Exception in thread "main" org.apache.seatunnel.core.starter.exception.CommandExecuteException: SeaTunnel job executed failed at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:202) at org.apache.seatunnel.core.starter.SeaTunnel.run(SeaTunnel.java:40) at org.apache.seatunnel.core.starter.seatunnel.SeaTunnelClient.main(SeaTunnelClient.java:34) Caused by: org.apache.seatunnel.engine.common.exception.SeaTunnelEngineException: org.apache.seatunnel.engine.common.exception.TaskGroupDeployException: java.lang.OutOfMemoryError: Metaspace at org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex.stateProcess(PhysicalVertex.java:561) [INFO] 2024-11-04 09:20:38.450 - [taskAppId=TASK-1519-5417926-7668604]:[127] - -> at org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex.updateTaskState(PhysicalVertex.java:392) at org.apache.seatunnel.engine.server.dag.physical.PhysicalVertex.makeTaskGroupDeploy(PhysicalVertex.java:319) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.lambda$stateProcess$19(SubPlan.java:627) at java.util.ArrayList.forEach(ArrayList.java:1257) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.stateProcess(SubPlan.java:623) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.updatePipelineState(SubPlan.java:360) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.stateProcess(SubPlan.java:609) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.updatePipelineState(SubPlan.java:360) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.stateProcess(SubPlan.java:596) at org.apache.seatunnel.engine.server.dag.physical.SubPlan.startSubPlanStateProcess(SubPlan.java:580) at org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan.lambda$stateProcess$3(PhysicalPlan.java:312) at java.util.ArrayList.forEach(ArrayList.java:1257) at org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan.stateProcess(PhysicalPlan.java:308) at org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan.updateJobState(PhysicalPlan.java:260) at org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan.stateProcess(PhysicalPlan.java:304) at org.apache.seatunnel.engine.server.dag.physical.PhysicalPlan.startJob(PhysicalPlan.java:289) at org.apache.seatunnel.engine.server.master.JobMaster.run(JobMaster.java:315) at org.apache.seatunnel.engine.server.CoordinatorService.lambda$submitJob$3(CoordinatorService.java:488) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at org.apache.seatunnel.core.starter.seatunnel.command.ClientExecuteCommand.execute(ClientExecuteCommand.java:194) ... 2 more ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version 1.8 ### Screenshots _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
