Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

ReqViewChange message handling #208

Merged
merged 2 commits into from
Jun 28, 2021

Conversation

sergefdrv
Copy link
Contributor

This pull request fully implements handling of ReqViewChange message type.

Resolves: #177

Sergey Fedorov added 2 commits June 24, 2021 17:51
Signed-off-by: Sergey Fedorov <sergey.fedorov@neclab.eu>
Once a replica collects a quorum of ReqViewChange messages for the
next view, it starts view change by generating a ViewChange message.
The generated message gets assigned the next UI and appended to the
message log. Since ViewChange message embeds all preceding certified
messages, the log is reset before appending it.

Signed-off-by: Sergey Fedorov <sergey.fedorov@neclab.eu>
@sergefdrv sergefdrv added the enhancement New feature or request label Jun 24, 2021
@sergefdrv sergefdrv added this to the v0.1.0 milestone Jun 24, 2021
@sergefdrv sergefdrv self-assigned this Jun 24, 2021
@sergefdrv sergefdrv requested a review from nhoriguchi as a code owner June 24, 2021 21:14
@sergefdrv sergefdrv changed the title Req view change handling ReqViewChange message handling Jun 24, 2021
@sergefdrv sergefdrv enabled auto-merge June 24, 2021 21:16
@sergefdrv sergefdrv merged commit e320139 into hyperledger-labs:master Jun 28, 2021
Copy link
Contributor

@nhoriguchi nhoriguchi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks nice to me, thank you.

@sergefdrv sergefdrv deleted the req-view-change-handling branch June 28, 2021 08:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement ReqViewChange message handling
2 participants