Details
Description
From IS-566:
In the attached log I see that libindy try to catchup pool transactions from 7 to 25 and one of the nodes (4th) do not response. And there are no logs after it, but libindy should after timeout detect and blacklist not responding nodes and resume catchup from others.
Logs from Node4: Desktop.7z