Performance collection unregistration during storage deletion #451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR addresses Performance collection unregistration during storage deletion
Currently 2 issues observed during storage deletion
This PR addresses these issues
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes ##440
Special notes for your reviewer:
One improvement is suggested on current performance collection.
To be tracked as part of below issue
#450
Detailed test report
Storage registration for performance collection:
Performance collection unregistration during storage delete
Restart after storage delete and no stale performance collection tasks:
Registration of multiple storages and unregistration of one storage:
Deletion of storage which is not registered for performance collection
Deletion of storage with some config file issue:
Release note: