-
Notifications
You must be signed in to change notification settings - Fork 220
feat: retry remove finalizer #1249
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
Conversation
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.
LGTM apart from some confusion on some of the comments / doc
@@ -19,7 +20,7 @@ class EventMarker { | |||
|
|||
public enum EventingState { | |||
/** Event but NOT Delete event present */ |
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.
This javadoc is confusing since it's unclear to which constant it applies…
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.
fixed
* if already processed mark for deletion we want to override that mark in case a custom | ||
* resource in the cache and not it is not marked for deletion. This could happen in an edge | ||
* case, when the resource is deleted while websocket was disconnected. And meanwhile a | ||
* resource with same ResourceID was deleted and created again. So resource should not be | ||
* marked received if processedMarkForDeletion present it's still marked for deletion, but | ||
* otherwise yes. | ||
*/ |
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.
I don't really understand the comment…
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.
reformulated, it's more like documenting an edge case that is not explicit, hope its better now
@@ -35,6 +37,8 @@ | |||
*/ | |||
class ReconciliationDispatcher<R extends HasMetadata> { | |||
|
|||
public static final int MAX_FINALIZER_REMOVAL_RETRY = 10; |
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.
Maybe that should be configurable from the ConfigurationService
?
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.
Would do it a separate PR TBH. Ideally this retry passes after 1-2 attemt, it's unlikely that there will be more than 3-4 finalizers.
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.
Yes, this should be done in a different PR for sure.
Kudos, SonarCloud Quality Gate passed! |
No description provided.