feat/node: send Ack on consensused message #1715
feat/node: send Ack on consensused message #1715
Conversation
cf4b2a4
to
dc8feb7
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.
Seem reasonable.
A couple of comments.
dc8feb7
to
c299256
Compare
4d608da
to
8f4bda5
Compare
|
Looks good, a minor comment |
8f4bda5
to
f000e7a
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.
Looks good.
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.
Looks good - just one comment that's not clear to me, but it might just be me, so not a blocker.
src/states/common/approved.rs
Outdated
| @@ -59,6 +59,7 @@ pub trait Approved: Relocated { | |||
| fn handle_neighbour_merge_event(&mut self) -> Result<(), RoutingError>; | |||
|
|
|||
| /// Handles an accumulated `SectionInfo` event. | |||
| /// If triggered during initial, an ack message shall not be sent out. | |||
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.
Could you rephrase the comment? I'm not sure what "triggered during initial" means.
925c5f6
to
3e8a934
Compare
627738d
to
4ca73ef
Compare
As the Ack will be a multi-cast message sent among section members, this could cause a 10-15% performance drop on the churn tests. As those tests invloves lost of membership change which will result in many section_info updates. Also, this commit contains a test requiring a setup of section splitting, which cost some time to complete normally.
4ca73ef
to
dec5b3b
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.
Looks good.
Closes #1666