You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
withTransactionError: Commit of transaction -2d8738205152fe557d63da9d11ca4d409f6be0470719057a5412535a71a53ed1 failed on peer.org1.example. com with status MVCC_READ_CONFLICT
#1482
Open
1234xxh opened this issue
Feb 12, 2023
· 2 comments
In Hyperledger Fabric, MVCC_READ_CONFLICT is an acceptable error response for which the client application needs to deal with see https://github.com/hyperledger/fabric-samples/tree/main/asset-transfer-basic/rest-api-typescript as an example of an application that is coded to handle this. I would suggest investing some time in hyperledger fabric to understand what an MVCC_READ_CONFLICT is but basically it means a key was modified after another transaction endorsed was the previous key value therefore that endorsed transaction cannot be committed. This kind of response is more likely to occur as the load is increased (you can design applications to avoid or reduce the possibility of this).
Caliper is just reports any failure to commit as a failure, it could in the future report it as a success or provide the capability for the workload to see this and be coded to retry the transaction.
This is not an issue with caliper
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Which Caliper version are you using?
v0.4.2
Which Node.JS version are you using?
v14.19.1
Which operating system are you using?
Ubuntu18.0.4
Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?
test smallbank
![image](https://user-images.githubusercontent.com/26919681/218298595-911ed4ad-b22e-4a08-8ff5-fb2f2b50bb8d.png)
![image](https://user-images.githubusercontent.com/26919681/218298639-2c9dc5bb-df6e-42a3-a7ad-8b7b2fac992f.png)
What was the observed incorrect behavior?
if "smallbank/config.yaml" tps is greater than 200, we get this error message
smallbank/config.yaml
txNumber: 100000
rateControl:
type: fixed-rate
opts:
tps: 500
Please provide the error logs and their surroundings.
Please provide your benchmark configuration file content, if possible.
Please provide your network configuration file content, if possible.
Please provide your workload module content, if possible.
Please provide any additional information you deem relevant to the error.
The text was updated successfully, but these errors were encountered: