Hyperledger Fabric 2.0.1 Documentationstayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability to enable the new capabilities only when member organizations 0 A major new release brings some additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time node to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the0 码力 | 760 页 | 10.21 MB | 1 年前3
Hyperledger Fabric 2.0.1 Documentationstayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability to enable the new capabilities only when member organizations 0 A major new release brings some additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time node to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the0 码力 | 533 页 | 8.37 MB | 1 年前3
Hyperledger Fabric 1.4.8 Documentationnode to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the same in production environments, the ordering nodes and peers can be upgraded simultaneously and on a rolling basis. In other words, you can upgrade the binaries in any order without bringing down the network output is good output. Upgrade the orderer containers Orderer containers should be upgraded in a rolling fashion (one at a time). At a high level, the orderer upgrade process goes as follows: 1. Stop the0 码力 | 699 页 | 9.02 MB | 1 年前3
Hyperledger Fabric 1.4.9 Documentationnode to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the same in production environments, the ordering nodes and peers can be upgraded simultaneously and on a rolling basis. In other words, you can upgrade the binaries in any order without bringing down the network is good output. 7.5.3 Upgrade the orderer containers Orderer containers should be upgraded in a rolling fashion (one at a time). At a high level, the orderer upgrade process goes as follows: 1. Stop the0 码力 | 483 页 | 7.48 MB | 1 年前3
Hyperledger Fabric 1.4.9 Documentationnode to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the same in production environments, the ordering nodes and peers can be upgraded simultaneously and on a rolling basis. In other words, you can upgrade the binaries in any order without bringing down the network output is good output. Upgrade the orderer containers Orderer containers should be upgraded in a rolling fashion (one at a time). At a high level, the orderer upgrade process goes as follows: 1. Stop the0 码力 | 701 页 | 9.02 MB | 1 年前3
Hyperledger Fabric 1.4 Documentationnode to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the same in production environments, the ordering nodes and peers can be upgraded simultaneously and on a rolling basis. In other words, you can upgrade the binaries in any order without bringing down the network is good output. 7.5.3 Upgrade the orderer containers Orderer containers should be upgraded in a rolling fashion (one at a time). At a high level, the orderer upgrade process goes as follows: 1. Stop the0 码力 | 483 页 | 7.48 MB | 1 年前3
Hyperledger Fabric 1.4.8 Documentationnode to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the same in production environments, the ordering nodes and peers can be upgraded simultaneously and on a rolling basis. In other words, you can upgrade the binaries in any order without bringing down the network is good output. 7.5.3 Upgrade the orderer containers Orderer containers should be upgraded in a rolling fashion (one at a time). At a high level, the orderer upgrade process goes as follows: 1. Stop the0 码力 | 483 页 | 7.48 MB | 1 年前3
Hyperledger Fabric 1.4 Documentationnode to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the same in production environments, the ordering nodes and peers can be upgraded simultaneously and on a rolling basis. In other words, you can upgrade the binaries in any order without bringing down the network output is good output. Upgrade the orderer containers Orderer containers should be upgraded in a rolling fashion (one at a time). At a high level, the orderer upgrade process goes as follows: 1. Stop the0 码力 | 701 页 | 9.02 MB | 1 年前3
Hyperledger Fabric 2.0 Documentationstayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability to enable the new capabilities only when member organizations 0 A major new release brings some additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time node to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the0 码力 | 821 页 | 10.22 MB | 1 年前3
Hyperledger Fabric 2.0 Documentationstayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability to enable the new capabilities only when member organizations 0 A major new release brings some additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time node to be at the same version level. In fact, supporting different version levels is what enables rolling upgrades of Fabric nodes. What is important is that networks and channels process things in the0 码力 | 573 页 | 8.52 MB | 1 年前3
共 57 条
- 1
- 2
- 3
- 4
- 5
- 6













