-
Notifications
You must be signed in to change notification settings - Fork 38
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
Harvest Poller panics from ZapiPerf:Volume collector #302
Labels
Comments
rahulguptajss
added a commit
that referenced
this issue
Jul 14, 2021
rahulguptajss
added a commit
that referenced
this issue
Jul 14, 2021
rahulguptajss
added a commit
that referenced
this issue
Jul 14, 2021
cgrinds
pushed a commit
that referenced
this issue
Jul 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Harvest Poller panics from ZapiPerf:Volume collector and doesn't recover
Environment
Provide accurate information about the environment to help us reproduce the issue.
harvest version 21.05.2-1 (commit ce091de) (build date 2021-06-14T20:31:09+0530) linux/amd64
bin/harvest start --config=foo.yml --collectors Zapi
]To Reproduce
![panic](https://user-images.githubusercontent.com/12505096/125549560-554a5082-702c-46fe-899a-29b89111de8a.png)
This seems to be due to when an instance goes missing from cache, which by default instance cache is 600s, the times I've experienced this issue is when a volume has been deleted. This particular occurrence a volume got deleted from the relevant cluster roughly 10mins before the panic occured.
Expected behavior
Poller should not panic when a volume gets deleted
Actual behavior
ZapiPerf:Volume collector causes a panic when volume gets deleted.
Possible solution, workaround, fix
N/A
The text was updated successfully, but these errors were encountered: