前言

在实验Hyperledger Fabric无排序组织以Raft协议启动多个Orderer服务、TLS组织运行维护Orderer服务中，我们已经完成了使用提供 TLS-CA 服务的 council 组织运行维护 Raft 协议的三个 orderer 节点。但目前我们都是在单个主机上启动 Fabric 网络，本文将尝试将 Hyperledger Fabric无排序组织以Raft协议启动多个Orderer服务、TLS组织运行维护Orderer服务 中的网络结构部署在多个主机上。

工作准备

本文工作

将 Hyperledger Fabric无排序组织以Raft协议启动多个Orderer服务、TLS组织运行维护Orderer服务 中网络部署至两台主机上—— DebianA 和 DebianB，其中 DebianA 维护 council 和 soft 组织及相关节点， DebianB 维护 web 和 hard 组织及相关节点，网络结构为（实验代码已上传至：https://github.com/wefantasy/FabricLearn 的 5_FabricNetworkByMultiHost 下）：

项 所属主机 运行端口 说明
council.ifantasy.net DebianA 7050 council 组织的 CA 服务， 为联盟链网络提供 TLS-CA 服务
orderer1.council.ifantasy.net DebianA 7051 orderer1 的排序服务
orderer1.council.ifantasy.net DebianA 7052 orderer1 的 admin 服务
orderer2.council.ifantasy.net DebianA 7054 orderer2 的排序服务
orderer2.council.ifantasy.net DebianA 7055 orderer2 的 admin 服务
orderer3.council.ifantasy.net DebianB 7057 orderer3 的排序服务
orderer3.council.ifantasy.net DebianB 7058 orderer3 的 admin 服务
soft.ifantasy.net DebianA 7250 soft 组织的 CA 服务， 包含成员： peer1 、 admin1
peer1.soft.ifantasy.net DebianA 7251 soft 组织的 peer1 成员节点
web.ifantasy.net DebianB 7350 web 组织的 CA 服务， 包含成员： peer1 、 admin1
peer1.web.ifantasy.net DebianB 7351 web 组织的 peer1 成员节点
hard.ifantasy.net DebianB 7450 hard 组织的 CA 服务， 包含成员： peer1 、 admin1
peer1.hard.ifantasy.net DebianB 7451 hard 组织的 peer1 成员节点

两个主机的相关信息为：

主机名 别名 网络地址 说明
DebianA host1 172.25.1.250 运行 council 和 soft
DebianB host2 172.25.1.251 运行 web 和 hard

实验准备

本文网络结构直接将 Hyperledger Fabric无排序组织以Raft协议启动多个Orderer服务、TLS组织运行维护Orderer服务 中创建的 4-2_RunOrdererByCouncil 复制为 5_FabricNetworkByMultiHost 并修改（建议直接将本案例仓库 FabricLearn 下的 5_FabricNetworkByMultiHost 目录拷贝到本地运行），文中大部分命令在 Hyperledger Fabric定制联盟链网络工程实践 中已有介绍因此不会详细说明。默认情况下，所有命令皆在 5_FabricNetworkByMultiHost 根目录下执行。

本系列所有实验都是在 VM ware 的 Debian 虚拟机（DebianA）下完成，本文会将 DebianA 虚拟机直接拷贝一份为 DebianB ，之后将会在 DebianA 下生成所有证书文件及通道文件，然后将文件复制一份到 DebianB 中再分别启动对应的网络。

配置文件

通过 docker 运行 fabric 网络总是需要解决不同节点间的通信问题（不能仅配置 DNS），目前主要有三种解决方案：

  • 在 docker-compose.yaml 中设置 extra_hosts 字段
  • 通过容器编排工具 docker swarm 实现
  • 通过容器编排工具 Kubernetes(K8S) 实现（后期尝试）

大规模容器编排管理目前最流行的就是 K8S ，后期本人也会朝此方向尝试，为了简便本文使用第一种方式实现不同主机的 docker 容器通信。具体实现方面，只需要在 compose/docker-compose.yaml 中的 orderer 服务和 peer 服务中添加下列代码，如 orderer1.council.ifantasy.net ：

  1.   orderer1.council.ifantasy.net:
  2.     container_name: orderer1.council.ifantasy.net
  3.     extends:
  4.       file: docker-base.yaml
  5.       service: orderer-base
  6.     environment:
  7.       - ORDERER_HOST=orderer1.council.ifantasy.net
  8.       - ORDERER_GENERAL_LOCALMSPID=councilMSP
  9.       - ORDERER_GENERAL_LISTENPORT=7051
  10.     volumes:
  11.       - ${LOCAL_CA_PATH}/council.ifantasy.net/registers/orderer1:${DOCKER_CA_PATH}/orderer
  12.       - ${LOCAL_ROOT_PATH}/data/genesis.block:${DOCKER_CA_PATH}/orderer/genesis.block
  13.     ports:
  14.       - 7051:7051
  15.       - 7052:8888
  16.       - 7053:9999
  17.     extra_hosts:
  18.       - "orderer1.council.ifantasy.net:172.25.1.250"
  19.       - "orderer2.council.ifantasy.net:172.25.1.250"
  20.       - "orderer3.council.ifantasy.net:172.25.1.251"

如果不进行上述配置，则会因无法通信而出现下列错误：

  1. Error: failed to send transaction: got unexpected status: SERVICE_UNAVAILABLE -- no Raft leader

证书和通道文件生成

网上很多相关教程都说明了将 Fabric 网络部署至多主机的方法[1] [2]，大部分教程都是在同一台主机上生成全部的组织证书文件再进行证书分发部署（包括本文），但必须说明的是这种方式必然不能用于生产环境，因为生成组织证书的那台主机将会拥有全部组织的访问权限。在生产环境中，应该每个组织通过自身的 CA 服务生成自身的组织证书，并由单个组织创建通道后使用 Hyperledger Fabric组织的动态添加和删除 中的方法将其它组织加入通道中。 此外，毫无疑问使用 cryptogen 的方式一次性生成所有证书比本文所使用的 fabric-ca 的方式简单很多（不必考虑 DNS 问题）。

启动 CA 服务

由于要通过 DebainA 生成所有证书文件，所以得先将本地 DNS 指向 DebianA （setDNSTemp.sh）：

  1. echo "127.0.0.1       council.ifantasy.net" >> /etc/hosts
  2. echo "127.0.0.1       soft.ifantasy.net" >> /etc/hosts
  3. echo "127.0.0.1       web.ifantasy.net" >> /etc/hosts
  4. echo "127.0.0.1       hard.ifantasy.net" >> /etc/hosts
  6. echo "127.0.0.1       orderer1.council.ifantasy.net" >> /etc/hosts
  7. echo "127.0.0.1       orderer2.council.ifantasy.net" >> /etc/hosts
  8. echo "127.0.0.1       orderer3.council.ifantasy.net" >> /etc/hosts
  10. echo "127.0.0.1       peer1.soft.ifantasy.net" >> /etc/hosts
  11. echo "127.0.0.1       peer1.web.ifantasy.net" >> /etc/hosts
  12. echo "127.0.0.1       peer1.hard.ifantasy.net" >> /etc/hosts

直接运行根目录下的 0_Restart.sh 即可完成本实验所需 CA 服务的启动。

  1. docker stop $(docker ps -aq)
  2. docker rm $(docker ps -aq)
  3. docker rmi $(docker images dev-* -q)
  4. # rm -rf orgs data
  5. docker-compose -f $LOCAL_ROOT_PATH/compose/docker-compose.yaml up -d council.ifantasy.net soft.ifantasy.net web.ifantasy.net hard.ifantasy.net

在前面的实验中，我们每次重启都删除所有的证书文件，但考虑到多机生成证书的复杂性，在这里只清除 docker 镜像而不删除证书文件。

注册账户

注册账户跟之前没什么不同，直接运行根目录下的 1_RegisterUser.sh 即可完成本实验所需用户的注册。

  1. council 用户注册：
  1. echo "Working on council"
  2. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/ca/crypto/ca-cert.pem
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/council.ifantasy.net/ca/admin
  4. fabric-ca-client enroll -d -u https://ca-admin:ca-adminpw@council.ifantasy.net:7050
  5. fabric-ca-client register -d --id.name admin1 --id.secret admin1 --id.type admin -u https://council.ifantasy.net:7050
  6. fabric-ca-client register -d --id.name orderer1 --id.secret orderer1 --id.type orderer -u https://council.ifantasy.net:7050
  7. fabric-ca-client register -d --id.name orderer2 --id.secret orderer2 --id.type orderer -u https://council.ifantasy.net:7050
  8. fabric-ca-client register -d --id.name orderer3 --id.secret orderer3 --id.type orderer -u https://council.ifantasy.net:7050
  9. fabric-ca-client register -d --id.name peer1soft --id.secret peer1soft --id.type peer -u https://council.ifantasy.net:7050
  10. fabric-ca-client register -d --id.name peer1web --id.secret peer1web --id.type peer -u https://council.ifantasy.net:7050
  11. fabric-ca-client register -d --id.name peer1hard --id.secret peer1hard --id.type peer -u https://council.ifantasy.net:7050
  1. soft 用户注册：
  1. echo "Working on soft"
  2. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/soft.ifantasy.net/ca/crypto/ca-cert.pem
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/soft.ifantasy.net/ca/admin
  4. fabric-ca-client enroll -d -u https://ca-admin:ca-adminpw@soft.ifantasy.net:7250
  5. fabric-ca-client register -d --id.name peer1 --id.secret peer1 --id.type peer -u https://soft.ifantasy.net:7250
  6. fabric-ca-client register -d --id.name admin1 --id.secret admin1 --id.type admin -u https://soft.ifantasy.net:7250
  1. web 用户注册：
  1. echo "Working on web"
  2. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/web.ifantasy.net/ca/crypto/ca-cert.pem
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/web.ifantasy.net/ca/admin
  4. fabric-ca-client enroll -d -u https://ca-admin:ca-adminpw@web.ifantasy.net:7350
  5. fabric-ca-client register -d --id.name peer1 --id.secret peer1 --id.type peer -u https://web.ifantasy.net:7350
  6. fabric-ca-client register -d --id.name admin1 --id.secret admin1 --id.type admin -u https://web.ifantasy.net:7350
  1. hard 用户注册：
  1. echo "Working on hard"
  2. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/hard.ifantasy.net/ca/crypto/ca-cert.pem
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/hard.ifantasy.net/ca/admin
  4. fabric-ca-client enroll -d -u https://ca-admin:ca-adminpw@hard.ifantasy.net:7450
  5. fabric-ca-client register -d --id.name peer1 --id.secret peer1 --id.type peer -u https://hard.ifantasy.net:7450
  6. fabric-ca-client register -d --id.name admin1 --id.secret admin1 --id.type admin -u https://hard.ifantasy.net:7450

组织证书构建

组织证书构建跟之前的实验一样，直接运行根目录下的 2_EnrollUser.sh 即可完成本实验所需证书的构建。

直接运行根目录下的 2_EnrollUser.sh 即可完成本实验所需证书的构建。

  1. 组织资产预处理：
  1. echo "Preparation============================="
  2. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/assets
  3. cp $LOCAL_CA_PATH/council.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/council.ifantasy.net/assets/ca-cert.pem
  4. cp $LOCAL_CA_PATH/council.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/council.ifantasy.net/assets/tls-ca-cert.pem
  6. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/assets
  7. cp $LOCAL_CA_PATH/soft.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/assets/ca-cert.pem
  8. cp $LOCAL_CA_PATH/council.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/assets/tls-ca-cert.pem
  10. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/assets
  11. cp $LOCAL_CA_PATH/web.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/web.ifantasy.net/assets/ca-cert.pem
  12. cp $LOCAL_CA_PATH/council.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/web.ifantasy.net/assets/tls-ca-cert.pem
  14. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/assets
  15. cp $LOCAL_CA_PATH/hard.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/assets/ca-cert.pem
  16. cp $LOCAL_CA_PATH/council.ifantasy.net/ca/crypto/ca-cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/assets/tls-ca-cert.pem
  17. echo "Preparation end=========================="
  1. council 证书构建：
  1. echo "Start Council============================="
  2. echo "Enroll Admin"
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/council.ifantasy.net/registers/admin1
  4. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/ca-cert.pem
  5. export FABRIC_CA_CLIENT_MSPDIR=msp
  6. fabric-ca-client enroll -d -u https://admin1:admin1@council.ifantasy.net:7050
  7. # 加入通道时会用到admin/msp，其下必须要有admincers
  8. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/admincerts
  9. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/admincerts/cert.pem
  11. echo "Enroll Orderer1"
  12. # for identity
  13. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1
  14. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/ca-cert.pem
  15. export FABRIC_CA_CLIENT_MSPDIR=msp
  16. fabric-ca-client enroll -d -u https://orderer1:orderer1@council.ifantasy.net:7050
  17. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1/msp/admincerts
  18. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1/msp/admincerts/cert.pem
  19. # for TLS
  20. export FABRIC_CA_CLIENT_MSPDIR=tls-msp
  21. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/tls-ca-cert.pem
  22. fabric-ca-client enroll -d -u https://orderer1:orderer1@council.ifantasy.net:7050 --enrollment.profile tls --csr.hosts orderer1.council.ifantasy.net
  23. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1/tls-msp/keystore/*_sk $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1/tls-msp/keystore/key.pem
  25. echo "Enroll Orderer2"
  26. # for identity
  27. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2
  28. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/ca-cert.pem
  29. export FABRIC_CA_CLIENT_MSPDIR=msp
  30. fabric-ca-client enroll -d -u https://orderer2:orderer2@council.ifantasy.net:7050
  31. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2/msp/admincerts
  32. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2/msp/admincerts/cert.pem
  33. # for TLS
  34. export FABRIC_CA_CLIENT_MSPDIR=tls-msp
  35. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/tls-ca-cert.pem
  36. fabric-ca-client enroll -d -u https://orderer2:orderer2@council.ifantasy.net:7050 --enrollment.profile tls --csr.hosts orderer2.council.ifantasy.net
  37. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2/tls-msp/keystore/*_sk $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2/tls-msp/keystore/key.pem
  39. echo "Enroll Orderer3"
  40. # for identity
  41. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3
  42. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/ca-cert.pem
  43. export FABRIC_CA_CLIENT_MSPDIR=msp
  44. fabric-ca-client enroll -d -u https://orderer3:orderer3@council.ifantasy.net:7050
  45. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3/msp/admincerts
  46. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3/msp/admincerts/cert.pem
  47. # for TLS
  48. export FABRIC_CA_CLIENT_MSPDIR=tls-msp
  49. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/council.ifantasy.net/assets/tls-ca-cert.pem
  50. fabric-ca-client enroll -d -u https://orderer3:orderer3@council.ifantasy.net:7050 --enrollment.profile tls --csr.hosts orderer3.council.ifantasy.net
  51. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3/tls-msp/keystore/*_sk $LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3/tls-msp/keystore/key.pem
  53. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/msp/admincerts
  54. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/msp/cacerts
  55. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/msp/tlscacerts
  56. mkdir -p $LOCAL_CA_PATH/council.ifantasy.net/msp/users
  57. cp $LOCAL_CA_PATH/council.ifantasy.net/assets/ca-cert.pem $LOCAL_CA_PATH/council.ifantasy.net/msp/cacerts/
  58. cp $LOCAL_CA_PATH/council.ifantasy.net/assets/tls-ca-cert.pem $LOCAL_CA_PATH/council.ifantasy.net/msp/tlscacerts/
  59. cp $LOCAL_CA_PATH/council.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/council.ifantasy.net/msp/admincerts/cert.pem
  60. cp $LOCAL_ROOT_PATH/config/config-msp.yaml $LOCAL_CA_PATH/council.ifantasy.net/msp/config.yaml
  61. echo "End council============================="
  1. soft 证书构建：
  1. echo "Start Soft============================="
  2. echo "Enroll Admin"
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/soft.ifantasy.net/registers/admin1
  4. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/soft.ifantasy.net/assets/ca-cert.pem
  5. export FABRIC_CA_CLIENT_MSPDIR=msp
  6. fabric-ca-client enroll -d -u https://admin1:admin1@soft.ifantasy.net:7250
  7. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/registers/admin1/msp/admincerts
  8. cp $LOCAL_CA_PATH/soft.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/registers/admin1/msp/admincerts/cert.pem
  10. echo "Enroll Peer1"
  11. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/soft.ifantasy.net/registers/peer1
  12. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/soft.ifantasy.net/assets/ca-cert.pem
  13. export FABRIC_CA_CLIENT_MSPDIR=msp
  14. fabric-ca-client enroll -d -u https://peer1:peer1@soft.ifantasy.net:7250
  15. # for TLS
  16. export FABRIC_CA_CLIENT_MSPDIR=tls-msp
  17. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/soft.ifantasy.net/assets/tls-ca-cert.pem
  18. fabric-ca-client enroll -d -u https://peer1soft:peer1soft@council.ifantasy.net:7050 --enrollment.profile tls --csr.hosts peer1.soft.ifantasy.net
  19. cp $LOCAL_CA_PATH/soft.ifantasy.net/registers/peer1/tls-msp/keystore/*_sk $LOCAL_CA_PATH/soft.ifantasy.net/registers/peer1/tls-msp/keystore/key.pem
  20. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/registers/peer1/msp/admincerts
  21. cp $LOCAL_CA_PATH/soft.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/registers/peer1/msp/admincerts/cert.pem
  23. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/msp/admincerts
  24. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/msp/cacerts
  25. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/msp/tlscacerts
  26. mkdir -p $LOCAL_CA_PATH/soft.ifantasy.net/msp/users
  27. cp $LOCAL_CA_PATH/soft.ifantasy.net/assets/ca-cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/msp/cacerts/
  28. cp $LOCAL_CA_PATH/soft.ifantasy.net/assets/tls-ca-cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/msp/tlscacerts/
  29. cp $LOCAL_CA_PATH/soft.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/soft.ifantasy.net/msp/admincerts/cert.pem
  30. cp $LOCAL_ROOT_PATH/config/config-msp.yaml $LOCAL_CA_PATH/soft.ifantasy.net/msp/config.yaml
  31. echo "End Soft============================="
  1. web 证书构建：
  1. echo "Start Web============================="
  2. echo "Enroll Admin"
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/web.ifantasy.net/registers/admin1
  4. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/web.ifantasy.net/assets/ca-cert.pem
  5. export FABRIC_CA_CLIENT_MSPDIR=msp
  6. fabric-ca-client enroll -d -u https://admin1:admin1@web.ifantasy.net:7350
  7. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/registers/admin1/msp/admincerts
  8. cp $LOCAL_CA_PATH/web.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/web.ifantasy.net/registers/admin1/msp/admincerts/cert.pem
  10. echo "Enroll Peer1"
  11. # for identity
  12. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/web.ifantasy.net/registers/peer1
  13. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/web.ifantasy.net/assets/ca-cert.pem
  14. export FABRIC_CA_CLIENT_MSPDIR=msp
  15. fabric-ca-client enroll -d -u https://peer1:peer1@web.ifantasy.net:7350
  16. # for TLS
  17. export FABRIC_CA_CLIENT_MSPDIR=tls-msp
  18. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/web.ifantasy.net/assets/tls-ca-cert.pem
  19. fabric-ca-client enroll -d -u https://peer1web:peer1web@council.ifantasy.net:7050 --enrollment.profile tls --csr.hosts peer1.web.ifantasy.net
  20. cp $LOCAL_CA_PATH/web.ifantasy.net/registers/peer1/tls-msp/keystore/*_sk $LOCAL_CA_PATH/web.ifantasy.net/registers/peer1/tls-msp/keystore/key.pem
  21. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/registers/peer1/msp/admincerts
  22. cp $LOCAL_CA_PATH/web.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/web.ifantasy.net/registers/peer1/msp/admincerts/cert.pem
  24. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/msp/admincerts
  25. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/msp/cacerts
  26. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/msp/tlscacerts
  27. mkdir -p $LOCAL_CA_PATH/web.ifantasy.net/msp/users
  28. cp $LOCAL_CA_PATH/web.ifantasy.net/assets/ca-cert.pem $LOCAL_CA_PATH/web.ifantasy.net/msp/cacerts/
  29. cp $LOCAL_CA_PATH/web.ifantasy.net/assets/tls-ca-cert.pem $LOCAL_CA_PATH/web.ifantasy.net/msp/tlscacerts/
  30. cp $LOCAL_CA_PATH/web.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/web.ifantasy.net/msp/admincerts/cert.pem
  31. cp $LOCAL_ROOT_PATH/config/config-msp.yaml $LOCAL_CA_PATH/web.ifantasy.net/msp/config.yaml
  32. echo "End Web============================="
  1. hard 证书构建：
  1. echo "Start Hard============================="
  2. echo "Enroll Admin"
  3. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/hard.ifantasy.net/registers/admin1
  4. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/hard.ifantasy.net/assets/ca-cert.pem
  5. export FABRIC_CA_CLIENT_MSPDIR=msp
  6. fabric-ca-client enroll -d -u https://admin1:admin1@hard.ifantasy.net:7450
  7. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/registers/admin1/msp/admincerts
  8. cp $LOCAL_CA_PATH/hard.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/registers/admin1/msp/admincerts/cert.pem
  10. echo "Enroll Peer1"
  11. export FABRIC_CA_CLIENT_HOME=$LOCAL_CA_PATH/hard.ifantasy.net/registers/peer1
  12. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/hard.ifantasy.net/assets/ca-cert.pem
  13. export FABRIC_CA_CLIENT_MSPDIR=msp
  14. fabric-ca-client enroll -d -u https://peer1:peer1@hard.ifantasy.net:7450
  15. # for TLS
  16. export FABRIC_CA_CLIENT_MSPDIR=tls-msp
  17. export FABRIC_CA_CLIENT_TLS_CERTFILES=$LOCAL_CA_PATH/hard.ifantasy.net/assets/tls-ca-cert.pem
  18. fabric-ca-client enroll -d -u https://peer1hard:peer1hard@council.ifantasy.net:7050 --enrollment.profile tls --csr.hosts peer1.hard.ifantasy.net
  19. cp $LOCAL_CA_PATH/hard.ifantasy.net/registers/peer1/tls-msp/keystore/*_sk $LOCAL_CA_PATH/hard.ifantasy.net/registers/peer1/tls-msp/keystore/key.pem
  20. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/registers/peer1/msp/admincerts
  21. cp $LOCAL_CA_PATH/hard.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/registers/peer1/msp/admincerts/cert.pem
  23. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/msp/admincerts
  24. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/msp/cacerts
  25. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/msp/tlscacerts
  26. mkdir -p $LOCAL_CA_PATH/hard.ifantasy.net/msp/users
  27. cp $LOCAL_CA_PATH/hard.ifantasy.net/assets/ca-cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/msp/cacerts/
  28. cp $LOCAL_CA_PATH/hard.ifantasy.net/assets/tls-ca-cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/msp/tlscacerts/
  29. cp $LOCAL_CA_PATH/hard.ifantasy.net/registers/admin1/msp/signcerts/cert.pem $LOCAL_CA_PATH/hard.ifantasy.net/msp/admincerts/cert.pem
  30. cp $LOCAL_ROOT_PATH/config/config-msp.yaml $LOCAL_CA_PATH/hard.ifantasy.net/msp/config.yaml
  31. echo "End Hard============================="

在上面操作完成后，已经暂时不需要 CA 服务了，因此先使用 docker stop $(docker ps -aq) 命令关闭正在运行的四个 CA 容器。

配置通道

配置通道的方法跟单机略有区别，由于我们预期将 peer 和 orderer 服务部署在不同的主机上，因此并不需要使用 docker-compose 启动其它容器，只需要生成通道文件就好。运行根目录下的 3_Configtxgen.sh 即可完成本实验所需通道配置。

  1. configtxgen -profile OrgsChannel -outputCreateChannelTx $LOCAL_ROOT_PATH/data/testchannel.tx -channelID testchannel
  2. configtxgen -profile OrgsChannel -outputBlock $LOCAL_ROOT_PATH/data/testchannel.block -channelID testchannel
  4. cp $LOCAL_ROOT_PATH/data/testchannel.block $LOCAL_CA_PATH/soft.ifantasy.net/assets/
  5. cp $LOCAL_ROOT_PATH/data/testchannel.block $LOCAL_CA_PATH/web.ifantasy.net/assets/
  6. cp $LOCAL_ROOT_PATH/data/testchannel.block $LOCAL_CA_PATH/hard.ifantasy.net/assets/

在以上步骤完成后，在 5_FabricNetworkByMultiHost 文件夹下的 data 和 orgs 目录中已经生成了全部网络所需的通道文件和组织证书文件，现在我们将 5_FabricNetworkByMultiHost 文件夹复制一份到 DebianB 主机上开始接下来的实验。以后每次重启网络只需要在每个主机上运行 0_Restart.sh 、 4_JoinChannel_host1.sh 、 4_JoinChannel_host2.sh 、 5_TestChaincode_host1.sh 、 5_TestChaincode_host2.sh 。

启动多机网络

配置 DNS

在上节中，我们为了方便在 DebianA 上生成证书，将所有域名映射都指向了 DebianA 自身，现在需要手动修改 /etc/hosts 文件并删除上节设置的 DNS 映射，然后设置新的 DNS 内容：

  1. echo "172.25.1.250       council.ifantasy.net" >> /etc/hosts
  2. echo "172.25.1.250       soft.ifantasy.net" >> /etc/hosts
  3. echo "172.25.1.251       web.ifantasy.net" >> /etc/hosts
  4. echo "172.25.1.251       hard.ifantasy.net" >> /etc/hosts
  6. echo "172.25.1.250       orderer1.council.ifantasy.net" >> /etc/hosts
  7. echo "172.25.1.250       orderer2.council.ifantasy.net" >> /etc/hosts
  8. echo "172.25.1.251       orderer3.council.ifantasy.net" >> /etc/hosts
  10. echo "172.25.1.250       peer1.soft.ifantasy.net" >> /etc/hosts
  11. echo "172.25.1.251       peer1.web.ifantasy.net" >> /etc/hosts
  12. echo "172.25.1.251       peer1.hard.ifantasy.net" >> /etc/hosts

同样，我们需要在 DebianB 上设置类似的 DNS 映射：

  1. echo "172.25.1.250       council.ifantasy.net" >> /etc/hosts
  2. echo "172.25.1.250       soft.ifantasy.net" >> /etc/hosts
  3. echo "172.25.1.251       web.ifantasy.net" >> /etc/hosts
  4. echo "172.25.1.251       hard.ifantasy.net" >> /etc/hosts
  6. echo "172.25.1.250       orderer1.council.ifantasy.net" >> /etc/hosts
  7. echo "172.25.1.250       orderer2.council.ifantasy.net" >> /etc/hosts
  8. echo "172.25.1.251       orderer3.council.ifantasy.net" >> /etc/hosts
  10. echo "172.25.1.250       peer1.soft.ifantasy.net" >> /etc/hosts
  11. echo "172.25.1.251       peer1.web.ifantasy.net" >> /etc/hosts
  12. echo "172.25.1.251       peer1.hard.ifantasy.net" >> /etc/hosts

启动容器并加入通道

DebainA

可以直接运行根目录下的 4_JoinChannel_host1.sh 脚本以使 DebianA 执行下列命令启动容器并加入通道：

  1. 启动本主机容器：
  1. source envpeer1soft
  2. docker-compose -f $LOCAL_ROOT_PATH/compose/docker-compose.yaml up -d council.ifantasy.net soft.ifantasy.net peer1.soft.ifantasy.net
  3. docker-compose -f $LOCAL_ROOT_PATH/compose/docker-compose.yaml up -d orderer1.council.ifantasy.net orderer2.council.ifantasy.net

此时 DebianA 运行的容器网络为：



2. 本主机排序服务加入通道：

  1. source envpeer1soft
  2. export ORDERER_ADMIN_TLS_SIGN_CERT=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1/tls-msp/signcerts/cert.pem
  3. export ORDERER_ADMIN_TLS_PRIVATE_KEY=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer1/tls-msp/keystore/key.pem
  4. osnadmin channel join -o orderer1.council.ifantasy.net:7052 --channelID testchannel --config-block $LOCAL_ROOT_PATH/data/testchannel.block --ca-file "$ORDERER_CA" --client-cert "$ORDERER_ADMIN_TLS_SIGN_CERT" --client-key "$ORDERER_ADMIN_TLS_PRIVATE_KEY"
  5. osnadmin channel list -o orderer1.council.ifantasy.net:7052 --ca-file $ORDERER_CA --client-cert $ORDERER_ADMIN_TLS_SIGN_CERT --client-key $ORDERER_ADMIN_TLS_PRIVATE_KEY
  6. export ORDERER_ADMIN_TLS_SIGN_CERT=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2/tls-msp/signcerts/cert.pem
  7. export ORDERER_ADMIN_TLS_PRIVATE_KEY=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer2/tls-msp/keystore/key.pem
  8. osnadmin channel join -o orderer2.council.ifantasy.net:7055 --channelID testchannel --config-block $LOCAL_ROOT_PATH/data/testchannel.block --ca-file "$ORDERER_CA" --client-cert "$ORDERER_ADMIN_TLS_SIGN_CERT" --client-key "$ORDERER_ADMIN_TLS_PRIVATE_KEY"
  9. osnadmin channel list -o orderer2.council.ifantasy.net:7055 --ca-file $ORDERER_CA --client-cert $ORDERER_ADMIN_TLS_SIGN_CERT --client-key $ORDERER_ADMIN_TLS_PRIVATE_KEY
  1. 本主机组织加入通道：
  1. source envpeer1soft
  2. peer channel join -b $LOCAL_CA_PATH/soft.ifantasy.net/assets/testchannel.block
  3. peer channel list

DebianB

可以直接运行根目录下的 4_JoinChannel_host2.sh 脚本以使 DebianB 执行下列命令启动容器并加入通道：

  1. 启动本主机容器：
  1. source envpeer1web
  2. docker-compose -f $LOCAL_ROOT_PATH/compose/docker-compose.yaml up -d web.ifantasy.net peer1.web.ifantasy.net hard.ifantasy.net peer1.hard.ifantasy.net
  3. docker-compose -f $LOCAL_ROOT_PATH/compose/docker-compose.yaml up -d orderer3.council.ifantasy.net

此时 DebianB 运行的容器网络为：



2. 本主机排序服务加入通道：

  1. source envpeer1web
  2. export ORDERER_ADMIN_TLS_SIGN_CERT=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3/tls-msp/signcerts/cert.pem
  3. export ORDERER_ADMIN_TLS_PRIVATE_KEY=$LOCAL_CA_PATH/council.ifantasy.net/registers/orderer3/tls-msp/keystore/key.pem
  4. osnadmin channel join -o orderer3.council.ifantasy.net:7058 --channelID testchannel --config-block $LOCAL_ROOT_PATH/data/testchannel.block --ca-file "$ORDERER_CA" --client-cert "$ORDERER_ADMIN_TLS_SIGN_CERT" --client-key "$ORDERER_ADMIN_TLS_PRIVATE_KEY"
  5. osnadmin channel list -o orderer3.council.ifantasy.net:7058 --ca-file $ORDERER_CA --client-cert $ORDERER_ADMIN_TLS_SIGN_CERT --client-key $ORDERER_ADMIN_TLS_PRIVATE_KEY
  1. 本主机组织加入通道：
  1. source envpeer1web
  2. peer channel join -b $LOCAL_CA_PATH/web.ifantasy.net/assets/testchannel.block
  3. peer channel list
  4. source envpeer1hard
  5. peer channel join -b $LOCAL_CA_PATH/hard.ifantasy.net/assets/testchannel.block
  6. peer channel list

安装并测试链码

由于通道更新需要根据策略进行顺序操作，所以不可以直接运行根目录下的 5_TestChaincode_host1.sh 脚本，而是在不同主机中分别按链码周期运行对应的脚本内容：

  1. DebianA 安装链码：
  1. source envpeer1soft
  2. # peer lifecycle chaincode package basic.tar.gz --path asset-transfer-basic/chaincode-go --label basic_1
  3. peer lifecycle chaincode install basic.tar.gz
  4. peer lifecycle chaincode queryinstalled
  1. DebianB 安装链码：
  1. source envpeer1web
  2. peer lifecycle chaincode install basic.tar.gz
  3. peer lifecycle chaincode queryinstalled
  4. source envpeer1hard
  5. peer lifecycle chaincode install basic.tar.gz
  6. peer lifecycle chaincode queryinstalled
  1. DebianA 批准链码：
  1. export CHAINCODE_ID=basic_1:06613e463ef6694805dd896ca79634a2de36fdf019fa7976467e6e632104d718
  2. source envpeer1soft
  3. peer lifecycle chaincode approveformyorg -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA  --channelID testchannel --name basic --version 1.0 --sequence 1 --waitForEvent --init-required --package-id $CHAINCODE_ID
  4. peer lifecycle chaincode queryapproved -C testchannel -n basic --sequence 1

此时使用以下命令查看链码批准情况：

  1. peer lifecycle chaincode checkcommitreadiness -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA --channelID testchannel --name basic --version 1.0 --sequence 1 --init-required



4. DebainB 批准链码：

  1. export CHAINCODE_ID=basic_1:06613e463ef6694805dd896ca79634a2de36fdf019fa7976467e6e632104d718
  2. source envpeer1web
  3. peer lifecycle chaincode approveformyorg -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA  --channelID testchannel --name basic --version 1.0 --sequence 1 --waitForEvent --init-required --package-id $CHAINCODE_ID
  4. peer lifecycle chaincode queryapproved -C testchannel -n basic --sequence 1
  5. source envpeer1hard
  6. peer lifecycle chaincode approveformyorg -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA  --channelID testchannel --name basic --version 1.0 --sequence 1 --waitForEvent --init-required --package-id $CHAINCODE_ID
  7. peer lifecycle chaincode queryapproved -C testchannel -n basic --sequence 1

此时再回到 DebianA 查看链码批准情况发现已同步：



5. DebainB 提交链码：

  1. source envpeer1web
  2. peer lifecycle chaincode commit -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA --channelID testchannel --name basic --init-required --version 1.0 --sequence 1 --peerAddresses peer1.soft.ifantasy.net:7251 --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --peerAddresses peer1.web.ifantasy.net:7351 --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE
  1. DebainB 初始化链码：
  1. source envpeer1web
  2. peer chaincode invoke --isInit -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA --channelID testchannel --name basic --peerAddresses peer1.soft.ifantasy.net:7251 --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --peerAddresses peer1.web.ifantasy.net:7351 --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE -c '{"Args":["InitLedger"]}'
  1. DebainA 调用链码：
  1. peer chaincode invoke -o orderer1.council.ifantasy.net:7051 --tls --cafile $ORDERER_CA --channelID testchannel --name basic --peerAddresses peer1.soft.ifantasy.net:7251 --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE --peerAddresses peer1.web.ifantasy.net:7351 --tlsRootCertFiles $CORE_PEER_TLS_ROOTCERT_FILE -c '{"Args":["GetAllAssets"]}'

参考

  1. KC Tam. Multi-Host Deployment for First Network (Hyperledger Fabric v2). CSDN. [2020-08-11] ︎

  2. 余府. Hyperledger Fabric 2.x 多机部署/分布式集群部署流程. CSDN. [2020-11-28] ︎

Hyperledger Fabric 部署在多个主机上的更多相关文章

  1. Hyperledger Fabric 部署

    Hyperledger Fabric 部署 Hyperledger Fabric需要使用Docker.Go环境. Docker环境安装 Docker环境安装 直接查看这一篇,安装好之后将当前用户非ro ...

  2. hyperledger fabric部署总结

    之前在有道云笔记上分享过,但想想还是搬到这里来吧,以后统一方便整理自己的知识进入正题.... 之前在调研 hyperledger fabric,其实部署说明官网都有,只是东西都是国外的照着操作也会遇到 ...

  3. HyperLedger Fabric部署与链码解读

    1.Fabric简介 Fabric是超级账本中的一个项目,用以推进区块链技术.和其他区块链类似,它也有一个账本,使用智能合约,且是一个参与者可以分别管理自身交易的系统.它是一个联盟链.Fabric与其 ...

  4. Hyperledger Fabric 智能合约开发及 fabric-sdk-go/fabric-gateway 使用示例

    前言 在上个实验 Hyperledger Fabric 多组织多排序节点部署在多个主机上 中,我们已经实现了多组织多排序节点部署在多个主机上,但到目前为止,我们所有的实验都只是研究了联盟链的网络配置方 ...

  5. 用Java为Hyperledger Fabric(超级账本)开发区块链智能合约链代码之部署与运行示例代码

    部署并运行 Java 链代码示例 您已经定义并启动了本地区块链网络,而且已构建 Java shim 客户端 JAR 并安装到本地 Maven 存储库中,现在已准备好在之前下载的 Hyperledger ...

  6. HyperLedger Fabric 1.1 手动部署单机单节点

    手动部署单机单节点 之前发布过官方的e2e部署方案,由于环境或是访问权限等各种问题,还是有相当一部分码友无法成功跑起来,故此,本章将来一次纯手动操作的集群部署. 主要需要的步骤如下: 1:环境整理 2 ...

  7. Centos7 HyperLedger Fabric 1.4 生产环境部署

    Kafka生产环境部署案例采用三个排序(orderer)服务.四个kafka.三个zookeeper和四个节点(peer)组成,共准备八台服务器,每台服务器对应的服务如下所示: kafka案例网络拓扑 ...

  8. 在Ubuntu中部署并测试HyperLedger Fabric 0.6

    最近开始研究区块链,对这个新兴的技术有了基本概念上的了解,所以打算基于一个开源项目做做实验.如果是做数字货币,那么比特币的源代码是最好的了,不过这算是区块链1.0吧,已经有很多改进的竞争币和山寨币出来 ...

  9. Hyperledger fabric 1.3版本的安装部署(原创多机多Orderer部署

    首先,我们在安装前,要考虑一个问题 Hyperledger Fabric,通过指定的节点进行背书授权,才能完成交易的存储 延伸开来,就是为了实现容错.高并发.易扩展,需要zookeeper来选择排序引 ...

随机推荐

  1. dotnet 6 使用 string.Create 提升字符串创建和拼接性能

    本文告诉大家,在 dotnet 6 或更高版本的 dotnet 里,如何使用 string.Create 提升字符串创建和拼接的性能,减少拼接字符串时,需要额外申请的内存,从而减少内存回收压力 本文也 ...

  2. luoguP5319 [BJOI2019]奥术神杖(分数规划，AC自动机DP)

    luoguP5319 [BJOI2019]奥术神杖(分数规划,AC自动机DP) Luogu 题解时间 难点在于式子转化,设有c个满足的子串,即求最大的 $ ans = \sqrt[c]{\prod_{ ...

  3. 恢复训练（学不动了摸会鱼） Pt. 1

    本来下午想把pre稿子写了,咕咕咕. 群论是啥也不会了,写个polya试试(手动doge)为什么博客媛没有emoji,以后万一自己搭博客一定要加上这个小东西 polya淼题:poj1286 先复吸一下 ...

  4. 麒麟系统开发笔记（二）：国产麒麟系统搭建Qt开发环境安装Qt5.12

    前言   开发国产应用,使用到银河麒麟V4,V10,本篇以V10记录,参照上一篇可安装V4.V7.V10三个版本,麒麟V4系自带了Qt,麒麟V10没有自带Qt,需要自己编译搭建环境.   银河麒麟V1 ...

  5. 输入URL回车之后，究竟发生了什么

    https://blog.csdn.net/androidstarjack/article/details/107031771 在浏览器输入URL回车之后发生了什么?(超详细版)   前言 这个问题已 ...

  6. leedCode

    https://blog.csdn.net/code_yilia/category_9851007.html https://blog.csdn.net/qq_17550379/article/det ...

  7. C++各种输入

    https://blog.csdn.net/qq_29735775/article/details/81165882 1.cin 2.cin.get() 3.cin.getline() 4.getli ...

  8. MariaDB数据库设置用户密码

    SET PASSWORD [FOR user] = { PASSWORD('some password') | OLD_PASSWORD('some password') | 'encrypted p ...

  9. elasticsearch 了解多少，说说你们公司 es 的集群架构，索 引数据大小，分片有多少，以及一些调优手段 。

    面试官:想了解应聘者之前公司接触的 ES 使用场景.规模,有没有做过比较大 规模的索引设计.规划.调优. 解答: 如实结合自己的实践场景回答即可. 比如:ES 集群架构 13 个节点,索引根据通道不同 ...

  10. 学习heartbeat-04 原理及部署

    1. Heartbeat介绍 1.1 Heartbeat作用 通过它可以将资源(IP及程序服务等资源)从一台故障计算机快速转移到另一台运转正常的机器继续提供服务,在实际生产应用场景中,heartbea ...