-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 empty queue condition for queue shutdown drain #7575
fix empty queue condition for queue shutdown drain #7575
Conversation
Once this is merged we should move forward with #7583 |
ping @guyboertje |
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
d983867
to
7e521c9
Compare
page test queue test move is_empty? at queue level new wrapped acked queue spec
7e521c9
to
aedf397
Compare
page test queue test move is_empty? at queue level new wrapped acked queue spec
page test queue test move is_empty? at queue level new wrapped acked queue spec
merged in master, 5.x and 5.5 |
present in 5.5.2+ |
@seang-es if you mean fixed in 5.5.2+ then yes, the fixed was merged in the 5.5 branch and included starting with 5.5.2. Labels are missing here, I will label it. |
This is a proposal to fix the second item of #7568 which aim at an acceptable fix to satisfy
ReadClient#empty?
without changing the semantic ofQueue.isFullyAcked()
The current implementation of
isFullyAcked()
for both theQueue
andPage
classes does not work to satisfy theReadClient#empty?
condition, see #7570.