Skip to content

Conversation

@meatballhat
Copy link
Contributor

to get a slice of tracked message values that have exceeded their deadline within a given time range into the past.

@meatballhat meatballhat requested a review from a team as a code owner October 14, 2025 16:56
@meatballhat
Copy link
Contributor Author

waiting on fix from #225

to get a slice of tracked message values that have exceeded their
deadline within a given time range into the past.
…line

so that the `GC` can delete them without double checking.
@meatballhat meatballhat force-pushed the client-deadline-exceeded branch from a164928 to 1699e64 Compare October 14, 2025 21:09
Copy link
Contributor

@NikhilSinha1 NikhilSinha1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this makes sense to me. When CordonDeadlineExceeded gets called we grab everything where the deadline is in the past and move it to the garbage set. Then before we do the HScan, we remove all the predictions in the garbage set and GC it, and then we do the HScan and clean up the removed keys

@meatballhat meatballhat merged commit e8996c9 into main Oct 14, 2025
2 checks passed
@meatballhat meatballhat deleted the client-deadline-exceeded branch October 14, 2025 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants