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
I am running the seatunnel cluster continuously, we are running the seatunnel on ec2 and after each run of a job for eg jdbc to jdbc the jvm size increases,....after each run the size increases continuously untill the memory in the ram is being occupied....if more space is required...it crashes the job...
I have tried to manage the jvm otptions as well....increased the heap memory size as well but no memory inprovements i have seen....
history-job-expire-minutes : also i have set it up to 5 mins....still no change
Search before asking
What happened
I am running the seatunnel cluster continuously, we are running the seatunnel on ec2 and after each run of a job for eg jdbc to jdbc the jvm size increases,....after each run the size increases continuously untill the memory in the ram is being occupied....if more space is required...it crashes the job...
I have tried to manage the jvm otptions as well....increased the heap memory size as well but no memory inprovements i have seen....
history-job-expire-minutes : also i have set it up to 5 mins....still no change
Is this a seatunnel bug or it can be resolved?
SeaTunnel Version
2.3.3
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
zeta
Java or Scala Version
java
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: