Details
-
Bug
-
Status: Complete
-
Highest
-
Resolution: Done
-
None
-
None
-
None
-
None
-
indy-node 1.2.275
-
Sprint 18.02 Stability, Sprint 18.03 Stability, DKMS
Description
Steps to Reproduce:
1. Setup the pool of 7 nodes and add 18 nodes manually.
2. Send 1 transaction manually.
3. Run python3 Perf_Add_nyms.py -n 10
=> transactions successfully written.
4. Run python3 Perf_Add_nyms.py -s 5 -n 100
=> transactions successfully written.
5. Run python3 Perf_Add_nyms.py -s 5 -n 10000
Actual Results:
Pool stopped working after writing of ~300 transactions.
Count of domain transactions: 291 on 1-7 nodes, 310 on 8 node, and 311 on remaining nodes.
Expected Results:
Pool should work.
Attachments
Issue Links
- relates to
-
INDY-1025 Pool stopped working and lost consensus while new node was performing a catch-up
-
- Complete
-