13813586515 commented on issue #7747:
URL: https://github.com/apache/seatunnel/issues/7747#issuecomment-2381037449

   > Your third picture and it’s wrong. Can provide more comprehensive info, ss 
zeta server run log and stack log
   
   2024-09-28 23:08:41,076 INFO  [o.a.s.e.s.CoordinatorService  ] 
[hz.main.generic-operation.thread-4] - [hadoop01]:55801 [seatunnel] [5.1] 
Received task end from execution TaskGroupLocation{jobId=892425438989647878, 
pipelineId=1, taskGroupId=30007}, state FAILED
   2024-09-28 23:08:41,104 INFO  [o.a.s.e.s.d.p.PhysicalVertex  ] 
[hz.main.generic-operation.thread-4] - Job future_hdqtls_供应商结算单 
(892425438989647878), Pipeline: [(1/1)], task: [pipeline-1 
[Source[0]-Jdbc]-SourceTask (8/10)] turned from state RUNNING to FAILED.
   2024-09-28 23:08:41,104 INFO  [o.a.s.e.s.d.p.PhysicalVertex  ] 
[hz.main.generic-operation.thread-4] - Job future_hdqtls_供应商结算单 
(892425438989647878), Pipeline: [(1/1)], task: [pipeline-1 
[Source[0]-Jdbc]-SourceTask (8/10)] state process is stopped
   2024-09-28 23:08:41,104 ERROR [o.a.s.e.s.d.p.PhysicalVertex  ] 
[hz.main.generic-operation.thread-4] - Job future_hdqtls_供应商结算单 
(892425438989647878), Pipeline: [(1/1)], task: [pipeline-1 
[Source[0]-Jdbc]-SourceTask (8/10)] end with state FAILED and Exception: 
com.hazelcast.core.HazelcastException: java.lang.OutOfMemoryError: Java heap 
space
        at 
com.hazelcast.internal.util.ExceptionUtil.lambda$static$0(ExceptionUtil.java:47)
        at 
com.hazelcast.internal.util.ExceptionUtil.peel(ExceptionUtil.java:125)
        at 
com.hazelcast.internal.util.ExceptionUtil.peel(ExceptionUtil.java:115)
        at com.hazelcast.internal.util.ExceptionUtil.peel(ExceptionUtil.java:68)
        at 
com.hazelcast.internal.util.ExceptionUtil.rethrow(ExceptionUtil.java:130)
        at 
com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:490)
        at 
com.hazelcast.map.impl.proxy.MapProxySupport.getInternal(MapProxySupport.java:371)
        at com.hazelcast.map.impl.proxy.MapProxyImpl.get(MapProxyImpl.java:123)
        at 
org.apache.seatunnel.engine.server.execution.TaskExecutionContext.getOrCreateMetricsContext(TaskExecutionContext.java:64)
        at 
org.apache.seatunnel.engine.server.task.SeaTunnelTask.init(SeaTunnelTask.java:128)
        at 
org.apache.seatunnel.engine.server.task.SourceSeaTunnelTask.init(SourceSeaTunnelTask.java:72)
        at 
org.apache.seatunnel.engine.server.TaskExecutionService$BlockingWorker.run(TaskExecutionService.java:715)
        at 
org.apache.seatunnel.engine.server.TaskExecutionService$NamedTaskWrapper.run(TaskExecutionService.java:1039)
        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)
   Caused by: java.lang.OutOfMemoryError: Java heap space
        at ------ submitted from ------.()
        at 
com.hazelcast.internal.util.ExceptionUtil.cloneExceptionWithFixedAsyncStackTrace(ExceptionUtil.java:336)
        at 
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.returnOrThrowWithGetConventions(InvocationFuture.java:112)
        at 
com.hazelcast.spi.impl.operationservice.impl.InvocationFuture.resolveAndThrowIfException(InvocationFuture.java:100)
        at 
com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:617)
        at 
com.hazelcast.map.impl.proxy.MapProxySupport.invokeOperation(MapProxySupport.java:479)
        ... 12 more
   
在master日志中发现了这么一段,后来观察发现,只要运行一段时间,imap配置在hdfs,就会出现内存溢出的情况,导致任务失败,我现在配置的历史任务存储时间是8个小时,理论上不会有内存溢出,是否是因为现在配置的imap在hdfs但是还是会全部加载到内存中?


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

Reply via email to