Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TopSQL's retention time does not work #127

Open
lilyjazz opened this issue Apr 24, 2022 · 1 comment
Open

TopSQL's retention time does not work #127

lilyjazz opened this issue Apr 24, 2022 · 1 comment
Labels
priority/p1 type/bug Something isn't working

Comments

@lilyjazz
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

What did you do?

Open topsql feature from March 21.

What did you expect to see?

topsql's retention time is 1 month and it does work, it should delete data that exceed retention time.

What did you see instead?

data for march 21 is still available.

What version of TiDB Dashboard are you using (./tidb-dashboard --version)?

6.0

kbNIPG4cUQ

This issue is from pingcap/tidb-dashboard#1218

@zhongzc
Copy link
Contributor

zhongzc commented Apr 25, 2022

Victoria-metrics does not clean up stale data in a partition in which still some valid data, so those stale data are visible before all data in that partition become stale.

Yesterday the part /data2/production/prometheus-9090/data/tsdb/data/small/2022_03/300830982_1104130_20220320163212.000_20220324122734.000_16DC81B605210EBA was removed by VM, data are as expected.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/p1 type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants