Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Have a per detector retention period #187

Open
kaituo opened this issue Jul 11, 2020 · 0 comments
Open

Have a per detector retention period #187

kaituo opened this issue Jul 11, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@kaituo
Copy link
Member

kaituo commented Jul 11, 2020

Is your feature request related to a problem? Please describe.
Currently, we have 90 day retention period for result index. We may want to add per detector retention period.

Describe the solution you'd like
1)We can use our own threadpool to do it, as going through all detector, and all results, is time consuming.
2)If previous delete fails, need to skip current delete.
3)how to deal with failed delete of a detector’s result in current run?
4)Reuse DeleteDetector (code deleted when bumping to 7.8, should find it in commits before) barring the cluster state part
5)Need to compact index since we may have small index after deleting (only those are never gonna be deleted is gonna be saved)

@kaituo kaituo added the enhancement New feature or request label Jul 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant