Details
Description
Environment:
indy-node 1.3.364
view change - on
logLevel - info
Steps to Reproduce:
1. Setup the pool of 25 nodes.
2. Run the load test from 5 clients.
Actual Result:
One of nodes was lagged on 291,395, the rest ones have wrote 307,554 and have stopped writing.
Logs were shared with dsurnin, archives names: view_change_info_log_pool_crashed_5_clients_p1.7z, view_change_info_log_pool_crashed_5_clients_p2.7z view_change_info_log_pool_crashed_5_clients_p3.7z
UPD: The issue was reproduced with load test from 1 client. Logs shared with dsurnin, archives names:
low_load_1client_stopped_writting_p1.7z
low_load_1client_stopped_writting_1315_p2.7z
low_load_1client_stopped_writting_1315_p3.7z
Acceptance Criteria:
- Find the cause, determine a Plan of Attack, and log the new task / epic.
Attachments
Issue Links
- relates to
-
INDY-1403 Applying txns from catchup reply in case several nodes sent replies with overlapping seqNo intervals
-
- Complete
-