使用作曲家更新结构链码时，MVCC_READ_CONFLICT错误 [英] MVCC_READ_CONFLICT error when update the fabric chaincode with composer

问题描述

我与五个对等方一起使用部署到光纤网络的作曲家. 今天，当我尝试使用composer bna文件更新结构链代码时. 但一个对等方返回错误:

I use composer deployed to the fabric network with five peers. Today when i try to update the fabric chaincode with composer bna file. but one peer return error:

Error: Peer localhost:13051 has rejected transaction '39ae7b9cf735ca56a7b9a20c60745206d94852a0a4f73d14cd6fd8813ef57566' with code MVCC_READ_CONFLICT  

通过此对等方的新dev *链代码docker生成了一个up. 但是，所有交易都会返回:

althrough the new dev* chaincode docker of this peer is generated an up. but,all the transaction will return:

 EXPIRED CHAINCODE 

所以我检查了该对等方的日志，发现它仍然使用旧版本的链码.

so i check this peer's log, found it still use the older version chaincode.

那么，是否有某种方式可以更新此对等方的链码版本? 可以直接由结构使用作曲家使用node.js生成的bna链码吗?

so if there is somehow to update this peer' chaincode version? could bna chaincode generated by composer using node.js be use directly by fabric?

推荐答案

发生的事情是您有一个状态分支，因此，同级将不同意(他们不同意要使用的链码的版本). Fabric 1.4(不确定哪个微版本)引入了将对等方重置为以前的块号的命令，您可以尝试使用这些命令将问题对等方重置回它们同意的程度，并让他们从再次订购. 如果没有，那么您将不得不从网络中删除该问题对等点，并创建新的对等点并将其加入频道.

What has happened is you have a state fork and as such peers are going to disagree (and they disagree on the version of chaincode to use). Fabric 1.4 (not sure which micro version) introduced commands to reset peers back to previous block numbers which you could try to use to reset your problem peer(s) back to a point where they were in agreement and let them pull the blocks from the orderer again. If not, then you will have to remove that problem peer(s) from your network and create new peers and join them to the channel.

这篇关于使用作曲家更新结构链码时，MVCC_READ_CONFLICT错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！