feat(保留期清理): 补齐 7 处只增不删的数据;修结果对象孤儿
审核发现一批表/元数据只增不删,且对象存储存在活跃泄漏: - module-cleanup 漏收 task_result_item / task_result_payload 的 payload 指针, 每晚删完行就在 json-server 桶留下孤儿对象;指针收集触顶从"截断后照样删整组" 改为任务组二分拆分,拆到单任务仍触顶则整组不删并记 error(截断会让指针随行消失) - 结果文件对象此前从不回收(只删 DB 行、对象留在桶里),现改为事务提交后 按 file_result / task_file_job 的 result_file_url 逐个回收 - 新增 7 个保留期清理:device_log_file 元数据、price_track_loop_run、撞款扫描行、 密钥用量日统计、紫鸟记忆过期行、PUBLISH 任务、BRAND 任务。后两者刻意不复用 module-cleanup(BRAND 不写 biz_file_task;PUBLISH 单任务可达数万行), 改为调各自既有的业务删除入口,保证结果对象与子表一起回收 - 未读通知补保留期(180 天,已读仍 90 天);ZiniaoMemoryStoreService.deleteExpired 此前全库无调用方(实现了没接线),现已挂定时任务 全部沿用既有范式:@Scheduled + 分布式锁单实例 + 分批 + 单轮批次数上限 + 失败只记日志。
This commit is contained in:
+62
@@ -0,0 +1,62 @@
|
||||
package com.nanri.aiimage.modules.ziniao.memory.service;
|
||||
|
||||
import com.nanri.aiimage.common.service.DistributedJobLockService;
|
||||
import lombok.RequiredArgsConstructor;
|
||||
import lombok.extern.slf4j.Slf4j;
|
||||
import org.springframework.beans.factory.annotation.Value;
|
||||
import org.springframework.scheduling.annotation.Scheduled;
|
||||
import org.springframework.stereotype.Service;
|
||||
|
||||
import java.time.Duration;
|
||||
|
||||
/**
|
||||
* 紫鸟记忆存储(biz_ziniao_memory_store)的过期行清理。
|
||||
*
|
||||
* <p>{@link ZiniaoMemoryStoreService#deleteExpired} 早就写好了,但**全库没有任何调用方**——
|
||||
* 属于典型的"实现了却没接线":过期行只有读取命中时才会被顺手删掉一行,
|
||||
* 店铺下线、改名后遗留的 key 行永远不会有人再读到,于是永久残留。
|
||||
*
|
||||
* <p>这里把它挂上定时任务。单独成类而不是直接给 store 加 {@code @Scheduled}:
|
||||
* store 是被广泛注入的存储组件,不该为了清理任务再依赖分布式锁。
|
||||
*/
|
||||
@Service
|
||||
@RequiredArgsConstructor
|
||||
@Slf4j
|
||||
public class ZiniaoMemoryExpiredCleanupService {
|
||||
|
||||
/** 单轮最多删除的批次数,剩余留给下一轮。 */
|
||||
static final int MAX_BATCHES_PER_RUN = 20;
|
||||
|
||||
private final ZiniaoMemoryStoreService memoryStoreService;
|
||||
private final DistributedJobLockService distributedJobLockService;
|
||||
|
||||
@Value("${aiimage.ziniao.memory-expired-cleanup-batch-size:500}")
|
||||
private int batchSize = 500;
|
||||
|
||||
@Scheduled(cron = "${aiimage.ziniao.memory-expired-cleanup-cron:0 50 4 * * *}")
|
||||
public void purgeExpired() {
|
||||
int size = Math.max(50, batchSize);
|
||||
|
||||
DistributedJobLockService.LockHandle lockHandle =
|
||||
distributedJobLockService.tryLock("ziniao:memory-expired-cleanup", Duration.ofMinutes(15));
|
||||
if (lockHandle == null) {
|
||||
log.info("[ziniao-memory] 过期行清理跳过:另一实例持锁");
|
||||
return;
|
||||
}
|
||||
try (lockHandle) {
|
||||
int totalDeleted = 0;
|
||||
int batches = 0;
|
||||
while (batches < MAX_BATCHES_PER_RUN) {
|
||||
int deleted = memoryStoreService.deleteExpired(size);
|
||||
batches++;
|
||||
totalDeleted += deleted;
|
||||
if (deleted < size) {
|
||||
break;
|
||||
}
|
||||
}
|
||||
log.info("[ziniao-memory] 过期行清理完成 deleted={} batches={}", totalDeleted, batches);
|
||||
} catch (Exception ex) {
|
||||
log.warn("[ziniao-memory] 过期行清理失败 msg={}", ex.getMessage(), ex);
|
||||
}
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user