Ignite TC Bot created IGNITE-28954:
--------------------------------------
Summary: TC Bot cleaner failure can prevent cached build-log
rotation
Key: IGNITE-28954
URL: https://issues.apache.org/jira/browse/IGNITE-28954
Project: Ignite
Issue Type: Bug
Reporter: Ignite TC Bot
Downloaded TeamCity build logs are cleaned only after the Ignite cache cleanup
completes. If cache cleanup fails while reading an incompatible persisted
value, the combined cleaner exits before file-log rotation starts, allowing
cached logs to grow without maintenance.
Root causes:
* Cache and file cleanup are exposed as one maintenance action and one
scheduled job.
* botDetectedDefects was omitted from the GridIntList migration cache list.
* Retention and technical-log size defaults are too permissive.
Proposed changes:
* Expose Cleaner.cleanLogs and Cleaner.cleanCaches as independent monitored
maintenance actions and scheduled jobs.
* Ensure a cache cleanup failure cannot block build-log rotation.
* Add botDetectedDefects to GridIntList migration and introduce a new migration
marker for existing databases.
* Retain build/cache entries for 110 days and downloaded build logs for 30 days.
* Cap rolled technical logs at 5 GiB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
