Details
-
Bug
-
Status: Complete
-
High
-
Resolution: Done
-
None
-
None
-
None
-
None
-
indy-anoncreds 1.0.32
indy-node 1.2.296
indy-plenum 1.2.235
libindy 1.3.0~363
libindy-crypto 0.2.0
python3-indy-crypto 0.2.0
-
Sprint 18.03 Stability, DKMS
Description
Steps to Reproduce:
1) Create pool from 4 nodes, where node2 is primary
2) Stop indy-node service on node4
3) Stop indy-node service on node2
4) Send some NYM from client
=> There is no feedback from pool (consensus is lost)
5) Start indy-node service on node4
=> "view change" was not happened after node start, consensus was not restored
6) Send some NYM from client
=> No "view change" by timeout or after request
7) Start indy-node service on node2
8) Send some NYM from client
=> "view change" was made after request, requests were written
Actual Results:
View change was not happened when the pool comes back to consensus with stopped primary node.
Expected Results:
View change should happen when the pool comes back to consensus with stopped primary node.
Attachments
Issue Links
- is duplicated by
-
INDY-1166 Unable to recover write consensus at n-f after f+1 descent
-
- Complete
-