Skip to content

DelayedFetchLogOperation will not be trigged to complete when replica number set to 1 #777

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
Open
1 of 2 tasks
luoyuxia opened this issue Apr 21, 2025 · 0 comments
Open
1 of 2 tasks

DelayedFetchLogOperation will not be trigged to complete when replica number set to 1 #777

luoyuxia opened this issue Apr 21, 2025 · 0 comments
Milestone
v0.7

Comments

@luoyuxia
Copy link
Collaborator

Search before asking

  • I searched in the issues and found nothing similar.

Fluss version

0.6.0 (latest release)

Please describe the bug 🐞

In #768, we directly remove the tryCompleteDelayedOperations in Replica#appendRecordsToLeader():

Image

This may cause DelayedFetchLogOperation not be trigged to complete when replica number set to 1 because there are no follower to fetch log from leader and trigger complete DelayedFetchLogOperation. In this case, DelayedFetchLogOperation will only finished when the wait time timeout.

Solution

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@wuchong wuchong added this to the v0.7 milestone Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.7
Development

No branches or pull requests
2 participants
@wuchong @luoyuxia