-
Notifications
You must be signed in to change notification settings - Fork 15.4k
KAFKA-10079: improve thread-level stickiness #8775
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
Merged
vvcephei
merged 23 commits into
apache:trunk
from
ableegoldman:10079-HA-for-in-memory-stores
Jun 10, 2020
Merged
Changes from 2 commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
9140097
WIP
ableegoldman 5083889
implemented stickiness
ableegoldman be11863
compiling tests
ableegoldman dc296fc
improve stickiness to the max
ableegoldman 4b8e96c
debugging last test
ableegoldman 8300d49
use sorted set for test
ableegoldman d40dd5a
checkstyle
ableegoldman 5cb6f40
add unit tests
ableegoldman 72e64ef
filter for statefulness in SPA
ableegoldman acb7a4c
fixing up tests
ableegoldman f580e63
bump log to INFO
ableegoldman 7c18e59
pull sorting into SPA
ableegoldman 96a6c23
checkstyle
ableegoldman d26d462
use UNKNOWN_OFFSET_SUM, always initialize lag
ableegoldman 6df10ca
remove no longer relevant new test
ableegoldman fc98357
fix/rename counter
ableegoldman b5cfd40
some cleanup
ableegoldman f83baf9
fixindentation
ableegoldman f0c5a19
simplify
ableegoldman ee384a9
fix bug caught in test
ableegoldman 168051c
Adding unit tests
ableegoldman 6b0f6fb
checkstyle
ableegoldman e921175
remove unused topic partitions
ableegoldman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Is this the right constant to represent "we don't know the lag"? Or did I mistake how this is going to be used?
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.
The value itself doesn't matter, just that it's constant across all tasks.
But I'm guessing you meant, why not use the existing
UNKNOWN_OFFSET_SUMsentinel, in which case the answer is probably just that I forgot about it. Anyway I did a slight additional refactoring beyond this, just fyi: instead of skipping the lag computation when we fail to fetch offsets, we now always initialize the lags and just pass in theUNKNOWN_OFFSET_SUMfor all stateful tasks when the offset fetch fails.