Empty sst file caused by system crashes

[ShiKaiWi]

Describe this problem

The phenomenon is that an empty sst file (stored on the local disk) was recorded in the manifest when the system crashed (actually ceresdb was running in a container and the container crashed).

Steps to reproduce

It is not easy to reproduce.

Expected behavior

The empty sst file should not be recorded in the manifest.

Additional Information

I inspected that the root cause is the missing fsync after finishing storing sst to disk and before recording it into manifest.