You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@seatunnel.apache.org by David Zollo <da...@gmail.com> on 2026/04/15 04:02:40 UTC

[DISCUSS] GitHub issue #10767 about historical runtime info retention in Zeta

Hi dev,

I opened a new GitHub issue to discuss whether SeaTunnel Zeta should
keep all historical job runtime information in IMap / StateStore, and
whether batch and streaming jobs should use different retention
strategies:

https://github.com/apache/seatunnel/issues/10767

Context:
- today we mainly have one global retention setting: history-job-expire-minutes
- batch jobs and streaming jobs usually have very different retention needs
- keeping too much historical runtime detail in distributed engine
state may increase pressure on memory / external IMAP storage

I think it would be helpful to discuss this in the GitHub issue
directly, so that the design discussion stays centralized and easier
to track.

Comments and alternative proposals are very welcome.


Best Regards,
David
Linkedin: https://www.linkedin.com/in/davidzollo