You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
Repeatedly releasing solt Zeta will call releaseTaskGroupResource after the normal task is completed
Release PipeResource This will result in duplicate release of solt
releaseTaskGroupResource Should it be for optimizing the release of resources during idle tasks in CDC, and should it only be used for CDC tasks #6526
SeaTunnel Version
dev
SeaTunnel Config
no
Running Command
no
Error Exception
2024-07-16 10:43:20,411 WARN org.apache.seatunnel.engine.server.resourcemanager.opeartion.ReleaseSlotOperation - wrong target release operation with job 865423301965512705 and slot profile SlotProfile{worker=[localhost]:5801, slotID=2, ownerJobID=865423301965512705, assigned=true, resourceProfile=ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, sequence='45b4e9f2-bbe0-4776-8f72-ea4ded8cf9a1'}, exception: org.apache.seatunnel.engine.server.service.slot.WrongTargetSlotException: Not exist this slot in slot service, slot profile: SlotProfile{worker=[localhost]:5801, slotID=2, ownerJobID=865423301965512705, assigned=true, resourceProfile=ResourceProfile{cpu=CPU{core=0}, heapMemory=Memory{bytes=0}}, sequence='45b4e9f2-bbe0-4776-8f72-ea4ded8cf9a1'}
at org.apache.seatunnel.engine.server.service.slot.DefaultSlotService.releaseSlot(DefaultSlotService.java:166)
at org.apache.seatunnel.engine.server.resourcemanager.opeartion.ReleaseSlotOperation.run(ReleaseSlotOperation.java:53)
at com.hazelcast.spi.impl.operationservice.Operation.call(Operation.java:189)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.call(OperationRunnerImpl.java:273)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:248)
at com.hazelcast.spi.impl.operationservice.impl.OperationRunnerImpl.run(OperationRunnerImpl.java:213)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.process(OperationThread.java:175)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.process(OperationThread.java:139)
at com.hazelcast.spi.impl.operationexecutor.impl.OperationThread.executeRun(OperationThread.java:123)
at com.hazelcast.internal.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:102)
Search before asking
What happened
Repeatedly releasing solt Zeta will call releaseTaskGroupResource after the normal task is completed
![image](https://private-user-images.githubusercontent.com/127465317/348921706-7ad3a28c-28d3-49e0-a361-6fe852af4d70.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MTY0NjMsIm5iZiI6MTczODkxNjE2MywicGF0aCI6Ii8xMjc0NjUzMTcvMzQ4OTIxNzA2LTdhZDNhMjhjLTI4ZDMtNDllMC1hMzYxLTZmZTg1MmFmNGQ3MC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwN1QwODE2MDNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yOGZiNDQ1NjExMjQ3YTMyZTdhMGI4MjU0NDc1NTQxNWUzZmNhMjNlOTRlYjZiZGUyYTI4MmViNmMxZWU3N2RmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.akkeFSwATE9rvIVBCc-mmYZ4GPHypnFfDPp-bw-gQQY)
Release PipeResource This will result in duplicate release of solt
releaseTaskGroupResource Should it be for optimizing the release of resources during idle tasks in CDC, and should it only be used for CDC tasks
#6526
SeaTunnel Version
dev
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: