Private data logs in fabric version 2.0 #fabric #fabric-chaincode


susheeldighade@...
 

Hello,
After the migration of our fabric setup from 1.4.4 version to 2.0, we have observed the private data logs getting appeared in the peer logs even though we are not using any private data collections in the chaincode. These logs weren't there for fabric 1.4.4 version. 

2020-05-07 12:36:42.909 UTC [gossip.privdata] prepareBlockPvtdata -> INFO 3664 Successfully fetched all eligible collection private write sets for block [3128] channel=mychannel

Also the block_and_pvtdata_commit latency has increased after the migration. Please clarify if there is any private data check for each transaction getting committed to the ledger in fabric 2.0 version. If so, is there any configuration by which this check can be bypassed.

We feel this private data activity is adding an additional latency in our TPS test results.

Join fabric@lists.hyperledger.org to automatically receive all group messages.