Hyperledger Fabric docker-compose CORE_PEER_GOSSIP_BOOTSTRAP
Hyperledger Fabric docker-compose CORE_PEER_GOSSIP_BOOTSTRAP
我有一些组织有超过 2 个同行。当我编辑 docker-compose-base.yaml 时,我不确定如何定义 CORE_PEER_GOSSIP_BOOTSTRAP。下面是我所做的,但是日志显示对等点无法连接到八卦对等点。这样做的正确方法是什么?提前致谢!
docker-撰写-base.yaml
peer0.caseManager.snts.com:
container_name: peer0.caseManager.snts.com
extends:
file: peer-base.yaml
service: peer-base
environment:
- CORE_PEER_ID=peer0.caseManager.snts.com
- CORE_PEER_ADDRESS=peer0.caseManager.snts.com:7051
- CORE_PEER_GOSSIP_BOOTSTRAP=[peer1.caseManager.snts.com:7051 peer2.caseManager.snts.com:7051]
- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.caseManager.snts.com:7051
- CORE_PEER_LOCALMSPID=CaseManagerMSP
volumes:
- /var/run/:/host/var/run/
- ../crypto-config/peerOrganizations/caseManager.snts.com/peers/peer0.caseManager.snts.com/msp:/etc/hyperledger/fabric/msp
- ../crypto-config/peerOrganizations/caseManager.snts.com/peers/peer0.caseManager.snts.com/tls:/etc/hyperledger/fabric/tls
- peer0.caseManager.snts.com:/var/hyperledger/production
ports:
- 9051:7051
- 9053:7053
日志 "docker-compose -p docker-compose.yaml up"
peer0.caseManager.snts.com | 2018-11-15 16:21:18.420 UTC [gossip/discovery] func1 -> WARN 023 Could not connect to {peer2.caseManager.snts.com:7051] [] [] peer2.caseManager.snts.com:7051] <nil> <nil>} : context deadline exceeded
peer0.caseManager.snts.com | 2018-11-15 16:21:18.420 UTC [gossip/discovery] func1 -> WARN 024 Could not connect to {[peer1.caseManager.snts.com:7051 [] [] [peer1.caseManager.snts.com:7051 <nil> <nil>} : context deadline exceeded
从同级的角度来看,Bootstrap 同级是来自同一组织的另一个同级,它可以在 bootstrap 期间联系到该同级并获取一些必要的信息以进行通信。 (see here)
您的设置看起来是正确的,而且您的 Peer0 比 Peer1 和 Peer2 启动得更早并且在启动过程中无法找到它们,这完全合理,但这并非不正常。你最终有任何错误吗?如果不是,这看起来像正常操作。
- CORE_PEER_GOSSIP_BOOTSTRAP=peer1.caseManager.snts.com:7051 peer2.caseManager.snts.com:7051
我有一些组织有超过 2 个同行。当我编辑 docker-compose-base.yaml 时,我不确定如何定义 CORE_PEER_GOSSIP_BOOTSTRAP。下面是我所做的,但是日志显示对等点无法连接到八卦对等点。这样做的正确方法是什么?提前致谢!
docker-撰写-base.yaml
peer0.caseManager.snts.com:
container_name: peer0.caseManager.snts.com
extends:
file: peer-base.yaml
service: peer-base
environment:
- CORE_PEER_ID=peer0.caseManager.snts.com
- CORE_PEER_ADDRESS=peer0.caseManager.snts.com:7051
- CORE_PEER_GOSSIP_BOOTSTRAP=[peer1.caseManager.snts.com:7051 peer2.caseManager.snts.com:7051]
- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.caseManager.snts.com:7051
- CORE_PEER_LOCALMSPID=CaseManagerMSP
volumes:
- /var/run/:/host/var/run/
- ../crypto-config/peerOrganizations/caseManager.snts.com/peers/peer0.caseManager.snts.com/msp:/etc/hyperledger/fabric/msp
- ../crypto-config/peerOrganizations/caseManager.snts.com/peers/peer0.caseManager.snts.com/tls:/etc/hyperledger/fabric/tls
- peer0.caseManager.snts.com:/var/hyperledger/production
ports:
- 9051:7051
- 9053:7053
日志 "docker-compose -p docker-compose.yaml up"
peer0.caseManager.snts.com | 2018-11-15 16:21:18.420 UTC [gossip/discovery] func1 -> WARN 023 Could not connect to {peer2.caseManager.snts.com:7051] [] [] peer2.caseManager.snts.com:7051] <nil> <nil>} : context deadline exceeded
peer0.caseManager.snts.com | 2018-11-15 16:21:18.420 UTC [gossip/discovery] func1 -> WARN 024 Could not connect to {[peer1.caseManager.snts.com:7051 [] [] [peer1.caseManager.snts.com:7051 <nil> <nil>} : context deadline exceeded
从同级的角度来看,Bootstrap 同级是来自同一组织的另一个同级,它可以在 bootstrap 期间联系到该同级并获取一些必要的信息以进行通信。 (see here)
您的设置看起来是正确的,而且您的 Peer0 比 Peer1 和 Peer2 启动得更早并且在启动过程中无法找到它们,这完全合理,但这并非不正常。你最终有任何错误吗?如果不是,这看起来像正常操作。
- CORE_PEER_GOSSIP_BOOTSTRAP=peer1.caseManager.snts.com:7051 peer2.caseManager.snts.com:7051