How does a downed peer connects back to the network in a fabric network

Question

I recently deployed the fabric network using Docker-compose, I was trying to simulate a downed peer. Essentially this is what happens:

1. 4 peers are brought online using docker-compose running a fabric network
2. 1 peer i.e the 4th peer goes down (done via docker stop command)
3. Invoke transactions are sent to the root peer which is verified by querying the peers after sometime (excluding the downed peer).
4. The downed peer is brought back up with docker start. Query transaction run fine on the always on peers but fail on the newly woken up peer.

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.

Answer 1

This might be due to the expected behavior of PBFT (assuming you are using it). As explained on issue 933,