You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "RocMarshal (Jira)" <ji...@apache.org> on 2024/08/13 02:30:00 UTC

[jira] [Created] (FLINK-36039) Support clean historical event handler records in autoscaler jdbc plugin

RocMarshal created FLINK-36039:
----------------------------------

             Summary: Support clean historical event handler records in autoscaler jdbc plugin
                 Key: FLINK-36039
                 URL: https://issues.apache.org/jira/browse/FLINK-36039
             Project: Flink
          Issue Type: Improvement
          Components: Autoscaler
            Reporter: RocMarshal


Currently, the autoscaler generates a large amount of historical data for event handlers. As the system runs for a long time, the volume of historical data will continue to grow. It is necessary to support automatic cleanup of data within a fixed period.

Based on the creation time timestamp, the following approach for cleaning up historical data might be a way:
 * Introduce the parameter {{job.autoscaler.event-handler.historical-ttl-duration}} (of type duration), which represents the storage time for historical data.
 * Introduce the parameter {{job.autoscaler.event-handler.historical-clean-interval}} (of type duration), which represents the interval between each data cleanup.

In the constructor of {{{}JdbcAutoScalerEventHandler{}}}, introduce a scheduled task. Also, add an internal interface method, {{{}close{}}}, to {{AutoScalerEventHandler}} and {{JobAutoScaler}} for stopping and cleaning up the relevant logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)