-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Fix to metadata refresh interruption #4679
Conversation
4f3b716
to
ced675f
Compare
3e05712
to
fc00cfc
Compare
ced675f
to
74b82fc
Compare
fc00cfc
to
420116d
Compare
74b82fc
to
05c2830
Compare
420116d
to
60045b7
Compare
05c2830
to
8090e71
Compare
60045b7
to
4657f99
Compare
bdccc8c
to
f0d63ab
Compare
78a5434
to
31fea0e
Compare
f9b1fa7
to
7bfe82b
Compare
31fea0e
to
cbf2c54
Compare
7bfe82b
to
e3bc31e
Compare
Metadata refreshes without partition leader change could lead to a loop of metadata calls at fixed intervals. Solved by stopping metadata refresh when all existing metadata is non-stale. Happening since 2.3.0
e3bc31e
to
44dc011
Compare
} | ||
rd_kafka_mock_request_destroy_array(requests, request_cnt); | ||
rd_usleep(100 * 1000, 0); | ||
while (matching_request_cnt < expected_cnt) { |
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.
If this criteria is never met, the test will be in infinite loop. Can we make sure that there is some deterministic terminate condition?
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 overall. Gave one comment.
Metadata refreshes without partition leader change could lead to a loop of metadata calls at fixed intervals. Solved by stopping metadata refresh when all existing metadata is non-stale. Happening since 2.3.0
Metadata refreshes without partition leader change could lead to a loop of metadata calls at fixed intervals. Solved by stopping metadata refresh when all existing metadata is non-stale. Happening since 2.3.0
Metadata refreshes without partition
leader change could lead to a loop of
metadata calls at fixed intervals.
Solved by stopping metadata refresh
when all existing metadata is non-stale.
Happening since 2.3.0
Closes #4577