Can I stop Peer Containers That Are Not Joined to Channel?

Yes. You can stop Peer Containers That Are Not Joined to Channel.

For example, you have 1 channel, "mychannel", and 4 peers. You know that only 2 of them are joined to the channel. You can stop the other peer containers.

1. List all peer containers:

$ docker ps -all | grep peer

hyperledger/fabric-peer:latest  "peer node start"  Up 3 hours  peer1.org2.example.com
hyperledger/fabric-peer:latest  "peer node start"  Up 3 hours  peer0.org1.example.com
hyperledger/fabric-peer:latest  "peer node start"  Up 3 hours  peer1.org1.example.com
hyperledger/fabric-peer:latest  "peer node start"  Up 3 hours  peer0.org2.example.com

2. Stop 2 peer containers that are not joined to the channel:

$ docker stop peer1.org1.example.com
$ docker stop peer1.org2.example.com

3. Do not remove their container images. You may want to use them later.

4. List all chaincode containers again:

$ docker ps --all | grep peer

hyperledger/fabric-peer:latest  "peer node start"  Up 3 hours  peer0.org1.example.com
hyperledger/fabric-peer:latest  "peer node start"  Up 3 hours  peer0.org2.example.com

5. Verify the chaincode instance:

$ docker exec -it cli bash

bash-4.4# peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
80

Only 2 peer containers are running now. The "expireDeadMembers" peer log messages will not show up any more.

⇒ Watch Chaincode Container Log

⇐ Watch Peer Container Log

⇑ Hyperledger Fabric Docker Containers

⇑⇑ Hyperledger Tutorials