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

Do not stop recovery STM when there are only relaxed consistency appends #65

Closed
mmaslankaprv opened this issue Nov 12, 2020 · 0 comments · Fixed by #79
Closed

Do not stop recovery STM when there are only relaxed consistency appends #65

mmaslankaprv opened this issue Nov 12, 2020 · 0 comments · Fixed by #79
Labels
area/raft

Comments

@mmaslankaprv
Copy link
Member

To limit latency we should trigger allow recovery STM sending data to followers immediately after they will be append to the leader log.
This was referenced Nov 12, 2020
Merged
Merged
mmaslankaprv pushed a commit to mmaslankaprv/redpanda that referenced this issue Sep 28, 2021
@twmb
Merge pull request redpanda-data#65 from unistack-org/master
841c44d 
when CommitRecords commit next offset to move forward
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/raft
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Last visible offset based on max offset replicated by majority mmaslankaprv/redpanda
1 participant
@mmaslankaprv