docker-compose - Fabric 网络 - 当关闭的对等点连接回网络时会发生什么？

Question

我最近使用 Docker-compose 部署了结构网络，我试图模拟一个宕机的节点。本质上是这样的:

1. 使用运行结构网络的 docker-compose 使 4 个对等节点联机
2. 1 个对等点，即第 4 个对等点出现故障(通过 docker stop 命令完成)
3. 调用事务被发送到根节点，在一段时间后通过查询节点(不包括已关闭的节点)进行验证。
4. 宕机的节点通过 docker start 恢复。查询事务在始终在线的节点上运行良好，但在新唤醒的节点上失败。

为什么第 4 个节点在启动后不同步区 block 链。是否需要采取措施来确保同步？还是作为流氓对等体被丢弃。

Answer 1

这可能是由于 PBFT 的预期行为(假设您正在使用它)。正如在 issue 933 上解释的那样,

I think what you're seeing is normal PBFT behavior: 2f+1 replicas aremaking progress, and f replicas are lagging slightly behind, and catchup occasionally.

If you shut down another peer, you should observethat the one you originally shut off and restarted will nowparticipate fully, and the network will continue to make progress. Aslong as the network is making progress, and the participating nodesshare a correct prefix, you're all good. The reason for f replicaslagging behind is that those f may be acting byzantine and progressdeliberately slowly. You cannot tell a difference between a slowercorrect replica, and a deliberately slower byzantine replica.Therefore we cannot wait for the last f stragglers. They will be leftbehind and sync up occasionally. If it turns out that some otherreplica is crashed, the network will stop making progress until onecorrect straggler catches up, and then the network will progressnormally.