Reputation:
I recently deployed the fabric network using Docker-compose, I was trying to simulate a downed peer. Essentially this is what happens:
Why isn't the 4th peer synchronizing the blockchain, once its up.Is there a step to be taken to ensure it does? Or is it discarded as a rogue peer.
Upvotes: 3
Views: 775
Reputation: 356
Hyperledger Fabric v0.6 does not support add peers dynamically. I am not sure for HF v1.0.
Upvotes: 0
Reputation: 18753
This might be due to the expected behavior of PBFT (assuming you are using it). As explained on issue 933,
I think what you're seeing is normal PBFT behavior: 2f+1 replicas are making progress, and f replicas are lagging slightly behind, and catch up occasionally.
If you shut down another peer, you should observe that the one you originally shut off and restarted will now participate fully, and the network will continue to make progress. As long as the network is making progress, and the participating nodes share a correct prefix, you're all good. The reason for f replicas lagging behind is that those f may be acting byzantine and progress deliberately slowly. You cannot tell a difference between a slower correct replica, and a deliberately slower byzantine replica. Therefore we cannot wait for the last f stragglers. They will be left behind and sync up occasionally. If it turns out that some other replica is crashed, the network will stop making progress until one correct straggler catches up, and then the network will progress normally.
Upvotes: 1