Do you mean the existing v1.4 peers are out of sync?
Or you are re-processing all transactions into a new network and the new network peers are out of sync with each other?
Or the new peers are out of sync relative to the old peers?
Which state database?
Why don't you do an inline upgrade of the peers rather than re-process the tranactions?
Can you identify the first transaction that is out of sync and look at the logs from that block height.
avinash.sachdewani2010---07/28/2021 11:48:00 PM---Hi Fabric Experts, Currently I am upgrading our network from HLF 1.4 to 2.2.
Date: 07/28/2021 11:48 PM
Subject: [EXTERNAL] [Hyperledger Fabric] Hyperledger 2.2 Peer Out of Sync issue #fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes
Sent by: fabric@...
Hi Fabric Experts, Currently I am upgrading our network from HLF 1.4 to 2.2. As our current HLF network using docker and kubernetes we decided to use below approach for the migration. Identify the last block using peer channel fetch ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd
Hi Fabric Experts,One Org2 Peer3 Orderer
Currently I am upgrading our network from HLF 1.4 to 2.2.
As our current HLF network using docker and kubernetes we decided to use below approach for the migration.
1. Identify the last block using peer channel fetch
2. Clone all the transactions blocks using peer channel fetch
3. Convert these blocks to JSON
4. Use the JSON objects to execute transactions using a fabric network.
We are running both HLF 1.4 and 2.2 network during the migration.
While transferring the transaction blocks network handling up to 65K transactions after that both peers going out of sync and maintaining different balance.
65K max I can reach so far sometime peer going out of sync as early as 5K transactions.
HLF 2.2 network Configuration:
Fabric Network 2.2.5
Please let me know if any one faced the similar issue and best way to solve the issue.