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
vmstorage: panic when graceful shutdown caused by push metrics #5548
Comments
#5548 Signed-off-by: hagen1778 <roman@victoriametrics.com>
#5548 Signed-off-by: hagen1778 <roman@victoriametrics.com>
Thanks for the ticket! The #5549 has been merged and will be included into the next release. |
…rics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for #5549 and the commit fe2d9f6 . Updates #5548
This prevents from possible nil pointer dereference issues when the storage metrics are read after the storage is stopped. Updates #5548
FYI, while the #5549 stops background push process from reading the metrics from the destroyed |
…rics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for #5549 and the commit fe2d9f6 . Updates #5548
This prevents from possible nil pointer dereference issues when the storage metrics are read after the storage is stopped. Updates #5548
#5548 Signed-off-by: hagen1778 <roman@victoriametrics.com>
…rics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for #5549 and the commit fe2d9f6 . Updates #5548
#5548 Signed-off-by: hagen1778 <roman@victoriametrics.com>
…rics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for #5549 and the commit fe2d9f6 . Updates #5548
#5548 Signed-off-by: hagen1778 <roman@victoriametrics.com>
…rics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for #5549 and the commit fe2d9f6 . Updates #5548
This prevents from possible nil pointer dereference issues when the storage metrics are read after the storage is stopped. Updates #5548
#5548 Signed-off-by: hagen1778 <roman@victoriametrics.com>
…rics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for #5549 and the commit fe2d9f6 . Updates #5548
This prevents from possible nil pointer dereference issues when the storage metrics are read after the storage is stopped. Updates #5548
FYI, the fix for this issue has been included in v1.87.13 LTS release. The fix will be included also into the latest release. |
FYI, the fix for this issue has been included in v1.93.10 LTS release. |
This issue has been addressed in v1.97.0. Closing it as fixed then. |
Describe the bug
I found that during the graceful shutdown of a vmstorage node, a panic was caused by pushing metrics。I can fix this bug. I will submit a Merge Request later to help VictoriaMetrics resolve this issue.
To Reproduce
None
Version
vmstorage-20231101-230002-tags-v1.93.7-cluster-0-g1415cd7cd
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: