- Welcome (Mark Ford)
- Planning for Sawtooth 1.2 Release (Shawn/Mark)
- Open RFCs (Shawn)
- Plan and action for pending batches in a validator node (Arun)
- Sawooth Raft - Feature addition: Change the Raft leader nodes (in round robin basis) based on a time or block interval (Manoj)
- Issue with "maximum_peer_connectivity" (Arun)
- Conclusion on builds in proxy network (Arun)
- Pending PRs
- Open Forum
...
- Plan and action for pending batches in a validator node. For example, in case of consensus engine like sawtooth-raft if an invalid transactions are not removed from follower nodes pending batches queue.
- Issue with "maximum_peer_connectivity"
- Name suggests that it limits maximum peers a validator can connect to. But in reality it appears to be limiting the number of connections (there's one inbound and outbound connection).
- Seen that there are multiple connections to the same validator node. Causing the node to reach "maximum_peer_connectivity" limit and reject all other peering requests. Experimented with just 4 nodes.
Sawtooth Raft
1. Approve below feature request for Raft. Changes are ready and tested. Can we raise a PR
Feature addition: Change the Raft leader nodes (in round robin basis) based on a time or block interval
This feature will initiate leadership transfer to next peer if either one of below condition is satisfied 1) Time elapsed in leader state exceeds threshold setting 2) Number of blocks committed by leader exceeds threshold setting Below are the Raft settings. Setting the value to 0 will disable the feature sawtooth.consensus.raft.leader_change_time_interval (time interval in millisec) sawtooth.consensus.raft.leader_change_block_interval (number of blocks)
Other topics:
- Conclusion on builds in proxy network
...