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.
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
Add finalizer for AddressPool #168
Add finalizer for AddressPool #168
Changes from all commits
1c73b42
578eaad
a6b9602
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me make sure.
isUsed
uses the direct API client, becauseAddressPool
can be removed in the situation that a client returns noAddressBlock
, but informer cache is staled(some AddressPools exists in fact). Is my understanding correct?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ysksuzuki
The primary reason of using
p.reader
is that it is used inpool.SyncBlocks()
. I don't want to increase cached resources.Typically the finalizer of
AddressPool
would be invoked in response to the deletion of the finalAddressBlock
.IsUsed()
should certainly return false, or else the finalizer will be delayed until the next forced reconcilliation. So using cache inIsUsed()
would be inappropriate.