DanielLeens commented on issue #10308: URL: https://github.com/apache/seatunnel/issues/10308#issuecomment-4956743822
Thanks for adding the production detail. The original issue here was about whether MinIO / S3-compatible storage could be used for this path at all. The new question about metadata growth, scheduled cleanup, and cluster restart failure looks like a different operational problem, so I do not think this closed thread is the best place to track it. Could you please open a new issue for that runtime behavior and include: 1. the exact SeaTunnel version 2. the current map-store / MinIO-related config with sensitive values masked 3. the startup error stack after a full cluster restart 4. the approximate metadata size or object count when startup begins to fail 5. whether the cleanup concern is about old abandoned job metadata, active checkpoint state, or both Those details will help us determine whether this is a missing retention mechanism, a startup-scan scalability issue, or an environment-specific configuration problem. -- 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]
