Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[ISSUE 7117] check message is in memory or not when init consumer offset for pop #7118

Merged
merged 1 commit into from Aug 9, 2023
Merged

[ISSUE 7117] check message is in memory or not when init consumer offset for pop #7118

merged 1 commit into from Aug 9, 2023

Conversation

xdkxlk
Copy link
Contributor

@xdkxlk xdkxlk commented Aug 4, 2023

Which Issue(s) This PR Fixes

Fixes #7117

Brief Description

How Did You Test This Change?

lollipopjin
lollipopjin approved these changes Aug 9, 2023
View reviewed changes
Copy link
Contributor

@lollipopjin lollipopjin left a comment

Choose a reason for hiding this comment

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

LGTM

@lollipopjin lollipopjin merged commit 04683ec into apache:develop Aug 9, 2023
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@lollipopjin lollipopjin lollipopjin approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Bug] When the broker scales up, the PopConsumer that uses Max to pull may have message loss
2 participants
@xdkxlk @lollipopjin