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.

Sign up for GitHub

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

Jump to bottom

DROP DATABASE is too slow for high cardinality databases #8118

Closed
e-dard opened this issue Mar 10, 2017 · 2 comments
Closed

DROP DATABASE is too slow for high cardinality databases #8118

e-dard opened this issue Mar 10, 2017 · 2 comments
Assignees
@e-dard
Labels
area/performance
Milestone
1.3.0

Comments

@e-dard
Copy link
Contributor

e-dard commented Mar 10, 2017

I have noticed for a while that DROP DATABASE is just too slow when series cardinality is reasonably high.
@e-dard e-dard self-assigned this Mar 10, 2017
@e-dard e-dard added this to the 1.3.0 milestone Mar 10, 2017
@e-dard e-dard mentioned this issue Mar 10, 2017
Merged
3 tasks
@sebito91
Copy link
Contributor

Have you looked and/or noticed that DROP MEASUREMENT seems to have the same behavior?

https://support.influxdb.com/hc/en-us/requests/5002

@e-dard
Copy link
Contributor Author

e-dard commented Mar 10, 2017

@sebito91 yes same underlying issue. Also affects DROP RETENTION POLICY. The issue is down to moving memory around in an unnecessary way. While this PR is a shortcut for the drop database fix, fixing the measurement and retention policy issues will require some more work. I'll try and take a look next week.

/cc @jwilder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@e-dard e-dard

Labels
area/performance
Projects
None yet
Milestone
1.3.0
Development

No branches or pull requests
2 participants
@e-dard @sebito91