[BUG] [performance] Infinite restart of one of the peers

[timofeevmd]

OS and Environment

linux, k8s

GIT commit hash

a62640d8a

Minimum working example / Steps to reproduce

find more information and technical details on the perf report - test 3

test was conducted with the waiting for responses from Gatling disabled. The goal of the test was to find the degradation point of Iroha after which the system does not recover.

Overall throughput based on Grafana data: 780 TPS per peer

Utilization:

CPU (core): Average of 1.83 across all peers

RAM (GB): Average of 1.65 across all peers

As a result of the test, it was found that one of the peers goes into an infinite restart loop (you can view the logfile in the test 3 report). The logs obtained before the presented logs only contain consensus records. The logs obtained afterward contain information only about the peer’s attempts to start up, which makes these logs uninformative

Actual result

Constant restart of one of the peers

Expected result

The peer's ability to restart and operate normally.

Logs

Log contents

Replace this text with a JSON log,
so it doesn't grow too large and has highlighting.

Who can help to reproduce?

@timofeevmd

Notes

No response