1.11.0
Release date: Nov 1st, 2019
Component Version Information
| Components | Version Numbers |
|---|---|
| indy-plenum | 1.11.0 |
| indy-node | 1.11.0 |
| sovrin | 1.1.60 |
Additional Information:
Please be careful with demoting/promoting/adding nodes (see Known Issues for details).
There are possible OOM issues during 3+ hours of target load or large catch-ups at 8 GB RAM nodes pool so 32 GB is recommended.
Major Changes
- Switch to PBFT View Change protocol
- Stability fixes
Detailed Changelog
Major Fixes
| Description | Additional Information | Ticket Number |
|---|---|---|
| One node doesn't catch up after promotion | INDY-2222 | |
| A Replica may process messages from other Replicas | INDY-2248 | |
| Up to F nodes are out of consensus after >3 hours of load | INDY-2268 | |
| A Node may not connect to another Node after restart | INDY-2274 | |
| Two View Changes happen during master or backup primary demotion | INDY-2247 |
Changes and Additions
| Description | Additional Information | Ticket Number |
|---|---|---|
| Debug: Integrate PBFT viewchanger service into current codebase | INDY-2140 | |
| Request missing ViewChange messages when receiving NewView | INDY-2178 | |
| Basic integration tests with a new View Change protocol need to pass | INDY-2223 | |
| Recover from a situation when View Change is finished on >= N-F of other nodes | INDY-2224 | |
| A Primary lagging behind a stable chedkpoints should not send NewView | INDY-2230 | |
| Do not stabilize checkpoint after the view change if a Replica doesn't have this checkpoint | INDY-2231 | |
| Save PrePrepare's BatchID in audit ledger and restore list of preprepares and prepares on node startup | INDY-2235 | |
| PBFT View Change Debug: Part 2 | INDY-2244 | |
| Optimize Propagate logic | INDY-2257 |
Known Issues
| Description | Additional Information | Ticket Number |
|---|---|---|
| All nodes need to select the same primary during view change | INDY-2262 | |
| A Node missing a View Change may not be able to finish it if NODE txns have been sent | INDY-2275 | |
| A new node joining the pool during the view change may not be able to start ordering immediately | INDY-2276 | |
| Summary: If there are NODE txns for adding/removing nodes interleaved with View Changes (not any view changes, but a specific subset), then either up to F or all Nodes may not be able to finish view change. Please see the details and conditions when it may happen in INDY-2262. |