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

Scraping service: stop scraping service instances on partial shutdown #417

Merged
merged 3 commits into from
Feb 18, 2021

Conversation

rfratto
Copy link
Member

@rfratto rfratto commented Feb 18, 2021

PR Description

This is needed for the config reloading, but is already handled today: when the overall Agent stop, it stops all intances, including ones retrieved via the scraping service. However, if just the scraping service was stopped, then its instances would continue running in the background. This fixes that problem.

Which issue(s) this PR fixes

Notes to the Reviewer

PR Checklist

  • CHANGELOG updated (not needed)
  • Documentation added (not needed)
  • Tests updated (not needed)

This is needed for the config reloading, but is already handled today:
when the overall Agent stop, it stops all intances, including ones
retrieved via the scraping service. However, if _just_ the scraping
service was stopped, then its instances would continue running in the
background. This fixes that problem.
@rfratto rfratto changed the title Scraping services: stop scraping service instances on partial shutdown Scraping service: stop scraping service instances on partial shutdown Feb 18, 2021
pkg/prom/ha/sharding.go Outdated Show resolved Hide resolved
@rfratto rfratto merged commit aa16bed into grafana:main Feb 18, 2021
@rfratto rfratto deleted the stop-ha-instances-on-shutdown branch February 18, 2021 18:49
@mattdurham mattdurham mentioned this pull request Sep 7, 2021
3 tasks
mattdurham pushed a commit that referenced this pull request Nov 11, 2021
…#417)

* stop scraping service instances on shutdown

This is needed for the config reloading, but is already handled today:
when the overall Agent stop, it stops all intances, including ones
retrieved via the scraping service. However, if _just_ the scraping
service was stopped, then its instances would continue running in the
background. This fixes that problem.

* log error when failing to delete config on sharding instance manager shutdown

* s/error/err for consistency
@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Apr 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants