Open chenziliang opened 3 months ago
We need validate
1. Create a stream without retention policy for the logstore
2. Using the REST API to reconfig the retention policy for the logstore. Without reboot, the retention policy shall kick in in 5 mins (10 mins maximum). If not, bug.
3. When max disk usage reached, validate if the background retention scheduler still works. It appeared not working in this case.
@shirley-gu-timeplus , please help verify the latest proton whether the retention policy is work: 1) from settings 2) from configuration
Describe what's wrong
k8s_metrics has the following defintion, but seem the retention policy didn't kick in for nativelog when disk usage reaches 90%.
How to reproduce
Error message and/or stacktrace
Additional context