dybyte opened a new issue, #12972: URL: https://github.com/apache/seatunnel/issues/12972
### 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 Finished jobs are stored in `engine_finishedJob*` maps with a TTL of `history-job-expire-minutes`. With IMap persistence (`FileMapStoreFactory`), they are reloaded without a TTL after all masters restart, and never expire again. Hazelcast does not delete expired entries from the MapStore, and `FileMapStore` does not persist the expiration time, so every finished job left in the WAL comes back with no TTL. Job history (and its logs) then grows forever and is reloaded into the heap on every full restart. A single-master deployment hits this on every restart. ### SeaTunnel Version dev ### SeaTunnel Config ```conf . ``` ### Running Command ```shell . ``` ### Error Exception ```log To reproduce: enable `map-store` for `engine*`, run a batch job to FINISHED, restart the master. Before the restart the entry in `engine_finishedJobState` has a TTL of `history-job-expire-minutes`; after it, `getEntryView(jobId).getTtl()` returns `Long.MAX_VALUE` (no expiration). ``` ### Zeta or Flink or Spark Version _No response_ ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [x] 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]
