Limits in Quorum Blockchain Service¶
Quorum Blockchain Service (QBS) has service and functional limits such as the number of nodes a member can have, consortium restrictions, and storage amounts.
Maximum limits on transactions and validator nodes depend on whether you provision QBS at development, business, or enterprise pricing tiers.
|Pricing tier||Max transaction nodes||Max validator nodes|
Business and enterprise tier nodes include two validator nodes. Four validator nodes are required to meet IBFT consensus, so your consortium network should have at least two QBS business or enterprise tier nodes.
Use the development tier for development, testing, and proof of concepts. Use the business or enterprise tier for production grade deployments, or if you are sending a high volume of private transactions.
Changing the pricing tier of an active network after member creation is not yet supported. If you do need to switch tiers, you can delete the original network and start a new network on the correct tier.
The maximum amount of storage that can be used per node for ledger data and logs is 1.8 terabytes.
Decreasing ledger and log storage size is not supported.
- Member names must be unique within a consortium.
- You can’t change member and consortium names.
- Development tier members can only exist in a consortium with other Development tier members.
- Development tier members that choose the Azure Spot Instance option during create can’t participate in a consortium.
- A consortium must have at least one administrator. If the only administrator in a consortium leaves the network, you must raise a support ticket to promote another member to be the new administrator.
- You can’t add members previously removed from the consortium. Rather, you must re-invite them to join the consortium and create a new member. Their existing member resources aren’t deleted in order to preserve historical transactions.