Re: Hyperledger 2.2 Peer Out of Sync issue #fabric #fabric-peer #fabric-sdk-node #fabric-endorser #fabric-kubernetes
To close the loop on this one... we found that two peers were configured to use a single CouchDB database, and therefore the peers were stepping on each other and getting inconsistency between peer data and CouchDB data. We will make it more clear in the docs that each peer must have their own dedicated CouchDB database.
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.
Hi Fabric Experts,
Fabric Network 2.2.5
Please let me know if any one faced the similar issue and best way to solve the issue.