-
Notifications
You must be signed in to change notification settings - Fork 515
fix: replication stuck when syncing large batches #4474
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
Conversation
69621e3
to
c45c5e6
Compare
c45c5e6
to
995fa2b
Compare
c7a8be7
to
c021365
Compare
Trace shows no record were sent, even thought slice was 1MB. So there should be at least 1 record arriving. Can you add more debugging to see how many bytes were received and why decoding failed?
|
If I understood well, these logs are saying that the records were not received by follower. But it's not saying about leader sending it. |
Here is leader sending to follower:
Follower receiving:
|
d8f51d7
to
a344916
Compare
a344916
to
22f453e
Compare
), | ||
)); | ||
} | ||
|
||
self.records.decode(&mut buf, version)?; |
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.
let's restore len validation
643d20b
to
2981229
Compare
2981229
to
2e35405
Compare
74684e3
to
a9c4554
Compare
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
Let's change in here |
a9c4554
to
ea52ffa
Compare
sure, done. |
Should fix replica sync problem: #4472
I also notice more perfomance with replicas now:
before:
now: