We have a fabric network with 2 orgs with 2 peers each for both organisations and 5 orderers . We are using fabric version 2.2.2. We have a single channel with a single chaincode. We have configured both peers of the org to be the anchor peers and have also configured CORE_PEER_GOSSIP_BOOTSTRAP,
CORE_PEER_GOSSIP_EXTERNALENDPOINT, CORE_PEER_LISTENADDRESS, CORE_PEER_ADDRESS, CORE_PEER_CHAINCODELISTENADDRESS and CORE_PEER_EVENTS_ADDRESS correctly. We are facing an issue with our application.
We are extensively using private data collection in our application. After installing the chaincode, we pushed 100 assets to store in the private data collection. We could see that all those assets got stored successfully in our both peers, then we started to ingest to store more data. After pushing almost 2500 assets, we started to observe that our peer2 stop sycing with peer1. So, we tried to restart the peer2. But, still we see the issue. When we check the channel info for peer1 we see that currently
We also observe that the block height of peer2 is increasing very slow. So, we are not sure if peer2 can get same block-height as peer1. Due to this we also see that the data we are inserting is not available in peer2. However, when we checked the transientstore of peer2, we could see the data there.
We also observe below logs in peer2.