超分类器织物对接-合成CORE_PEER_GOSSIP_BOOTSTRAP

Question

我有一些组织，有两个以上的同行。当我编辑docker-compose-base.yaml时，我不知道如何定义CORE_PEER_GOSSIP_BOOTSTRAP。下面是我所做的，但是日志显示这个对等者无法连接到那些流言蜚语的同行。怎样才是正确的方法呢？提前谢谢你！

docker-compose-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

日志的“码头-组成-p码头-复合.docker 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

Answer 1

从同侪的角度来看，Bootstrap对等体是来自同一个组织的另一个对等体，它可以在引导过程中与其联系，并获得一些必要的信息来进行交流。(请看这里)

您的设置看起来是正确的，而且您的Peer0比Peer1和Peer2启动得更早，并且在启动过程中找不到这些，这是完全合理的，但这并不奇怪。你最后有什么错误吗？如果没有，这看起来就像正常的操作。

Answer 2

- CORE_PEER_GOSSIP_BOOTSTRAP=peer1.caseManager.snts.com:7051 peer2.caseManager.snts.com:7051