-
Notifications
You must be signed in to change notification settings - Fork 569
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
mimir-tool: analyse prometheus: ux: refactor / resiliency / concurrency #3062
Labels
Comments
FWIW I think it makes sense. Some notes on your suggestions:
we already use dskit's concurrency package to do that, see the ruler
we already use dskit's backoff - example |
3 tasks
anilmisirlioglu
added a commit
to anilmisirlioglu/mimir
that referenced
this issue
Nov 8, 2022
Fixes grafana#3062 Signed-off-by: Anıl Mısırlıoğlu <[email protected]> Co-authered-by: Furkan Türkal <[email protected]> Co-authered-by: Ayşe Sert <[email protected]>
Logiraptor
pushed a commit
that referenced
this issue
Nov 9, 2022
Fixes #3062 Signed-off-by: Anıl Mısırlıoğlu <[email protected]> Co-authered-by: Furkan Türkal <[email protected]> Co-authered-by: Ayşe Sert <[email protected]> Signed-off-by: Anıl Mısırlıoğlu <[email protected]>
masonmei
pushed a commit
to udmire/mimir
that referenced
this issue
Dec 16, 2022
Fixes grafana#3062 Signed-off-by: Anıl Mısırlıoğlu <[email protected]> Co-authered-by: Furkan Türkal <[email protected]> Co-authered-by: Ayşe Sert <[email protected]> Signed-off-by: Anıl Mısırlıoğlu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
analyse_prometheus.go is not cleanly written and contains lots of duplicate logics. Also it does not have any resiliency and concurrency mechanism if we run against very large Prometheus instance. (it takes a few hours or longer). Here are my two cents:
v1api.Query()
sync.Map
andsync.RWMutex
(for concurrency safety)cc @anilmisirlioglu
The text was updated successfully, but these errors were encountered: