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
Optimize kinesis ingestion task assignment after resharding #12235
Optimize kinesis ingestion task assignment after resharding #12235
Changes from 7 commits
dc96518
f8dd11e
df9a72e
7c708dd
5311126
fde9873
2b1f4ad
82a89a8
2353b97
a1c5b1a
7239f05
8908f87
b975f82
31fd84c
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.
Should these be in thread-safe container, or have access be protected with lock?
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.
Thanks for pointing this out, @zachjsh.
This code would be executed by the
SeekableStreamSupervisor
while executing aRunNotice
(scheduled when status of a task changes) as well as aDynamicAllocationTasksNotice
(scheduled for auto-scaling). There is a possibility of contention between these two executions.We can make the part where the caches are updated
synchronized
.Just changing these two caches to a
Concurrent
version might not be enough as a whole new list of active shards is fetched inupdateClosedShardCache()
and the caches must be updated with this new state before any other action is performed.cc: @AmatyaAvadhanula
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.
Synchronizing the whole method
updateClosedShardCache
would actually be preferable because the state returned by two subsequent calls torecordSupplier.getShards()
can be different.So this call should happen inside the synchronized block, as should the calls to
recordSupplier.isClosedShardEmpty()
.I hope this doesn't cause bottlenecks though.
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 whole method has been synchronized. Thanks!
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.
nit - this should be called computeIgnorablePartitionIds() or loadIgnorablePartitionIds()
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 current verb indicates that it is just a getter but behind the scenes it can do network calls etc to fetch the partition ids.
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.
done