You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "goutamadwant (via GitHub)" <gi...@apache.org> on 2026/08/28 00:16:05 UTC

Re: [I] [Discussion] IMAP information retention policy, excessive engine_runningJobMetrics data causing disk space exhaustion [seatunnel]

goutamadwant commented on issue #11125:
URL: https://github.com/apache/seatunnel/issues/11125#issuecomment-5446757606

   @DanielLeens @davidzollo I started tracing this against current `dev` and found that #11244 already implemented the phase 1 behavior after this discussion.
   
   `engine_runningJobMetrics` is now excluded from persistent IMAP storage while the in-memory metrics flow stays unchanged. Other engine state maps are not affected, and the restart behavior is documented in both English and Chinese.
   
   I also reran `FileMapStoreTest` locally and all 3 tests pass.
   
   The current implementation makes the exclusion unconditional rather than adding a config switch. Does this cover #11125 completely, or do we still want a separate opt-in option for persisting running metrics?


-- 
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: commits-unsubscribe@seatunnel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org