apache/seatunnel

[Bug] [imap] engine_runningJobMetrics size too long, imap monitoring data is too large

Open

#8,558 opened on Jan 20, 2025

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Java (6,897 stars) (1,432 forks)batch import
bughelp wanted

Description

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

In split mode, after MySQL CDC runs for a period of time, the imap is stored on the local disk and takes up too much space, a full 200GB. The parameters configured as follows do not clear the data. If this continues, the task will definitely not be able to run.

seatunnel: engine: history-job-expire-minutes: 1440 telemetry: logs: scheduled-deletion-enable: true

SeaTunnel Version

2.3.9

SeaTunnel Config

MySQL的cdc

Running Command

MySQL的cdc

Error Exception

MySQL的cdc

Zeta or Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

Image

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
java
Domain
backenddata
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
basic understanding of SeaTunnel enginefamiliarity with IMAP storage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue reports that in split mode, the IMAP (In Memory Aggregate Store) size grows unboundedly, taking up to 200GB despite configured cleanup settings. The root cause likely lies in the engine's monitoring data cleanup logic not respecting the `history job expire minutes` or `scheduled deletion enable` config. The fix should involve examining the engine's `engine runningJobMetrics` storage and ensuring the scheduled deletion works correctly for IMAP data in split mode. Look into the engine module, particularly the telemetry and state management code, to understand how metrics are stored and cleaned. The issue is documented at https://github.com/apache/seatunnel/issues/8558, and no PR is linked. The maintainers have not yet provided a definitive direction, so investigating the cleanup mechanism and proposed fix is needed.