-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix statement-store gossiping #9912
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
base: master
Are you sure you want to change the base?
Conversation
860f41c
to
7b8aeb1
Compare
/cmd prdoc --audience node_dev --bump patch |
…e_dev --bump patch'
All GitHub workflows were cancelled due to failure one of the required jobs. |
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.
Some tests would be nice for the new send logic.
|
||
// Size exceeded - split the chunk | ||
let split_factor = | ||
(encoded.len() / MAX_STATEMENT_NOTIFICATION_SIZE as usize) + 1; |
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.
(encoded.len() / MAX_STATEMENT_NOTIFICATION_SIZE as usize) + 1; | |
(encode_size / MAX_STATEMENT_NOTIFICATION_SIZE as usize) + 1; |
if new_chunk_size == 0 { | ||
log::warn!( | ||
target: LOG_TARGET, | ||
"Statement too large ({} KB), skipping", |
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.
It would be nice to exactly skip the one statement that is problematic and not maybe more.
Description
Fixes gossiping and scalability issues in the statement-store networking.
Integration
Internal optimizations to the gossip protocol. No downstream changes required.