5.2.0版本Broker意外断电重启后，store/config/timermetrics文件损坏，无法启动

[610991905]

单机版本服务器断电重启后，broker启动报store/config/timermetrics文件损坏，导致broker无法启动。这个是bug吗？还是说设计的时候没有考虑过意外断电自恢复的情况？

另外观察这个文件，发现即使这个store/config/timermetrics文件内容没有任何更新，依然会每秒被删除1次，然后重新生成。这个机制背后对应的原因是什么？为什么这么设计呢？

因为我们是在纯私有化场景使用，期望能够支撑意外断电自恢复，而不是还需要手工重建数据进行恢复。

[GenerousMan]

This problem should be a bug in the parsing process of the timermetric file. I can fix this problem later. As for the disk flushing once per second, it is a simple regular update strategy without any deeper design purpose and meaning.

[610991905]

yes，is a bug, i found it。
org.apache.rocketmq.store.timer.TimerMetrics.persist()

org.apache.rocketmq.common.ConfigManager.loadBak()

the same promble in org.apache.rocketmq.broker.transaction.TransactionMetrics.persist()

[610991905]

the disk flushing once per second Increased the probability of problems occurring，is not necessary

[GenerousMan]

the disk flushing once per second Increased the probability of problems occurring，is not necessary

I get it. I will try to fix this problem.

[GenerousMan]

the disk flushing once per second Increased the probability of problems occurring，is not necessary

https://github.com/apache/rocketmq/pull/9413/files
The problem may be fixed through this pull request. Before deleting the original file, the bak file should be flushed.

[GenerousMan]

Did you back up the timermetrics file at that time? You can check whether it is indeed an unclosed json file.