toggle quoted messageShow quoted text
To my understanding, consider this (Key, Value, version).
for every successful update on a key, both values and the version are changes, such that the value will be committed, and the version is increased by one.
So, it can happen that, a current transaction is reading a key, which version say is 5 and the value is 10 for example. During that, it happens that an in-flight transaction managed to be committed, causing the version to be 6 now instead of 5.
Now, back to that transaction that is currently trying to update a key based on version 5, agnostic to what happened to the key meanwhile.
When peers try to commit the current transaction, there will the conflict of the version occurs.
This is my attempt to explain the MVCC conflict. Again, this is my own impression, which needs to be confirmed by others with more insight on the matter.
On Tue, 19 May 2020 at 08:43, Prasanth Sundaravelu <prasanths96@...
It's a classic error that prevents double spending / race condition.
You must be trying to update the same key over and over when loading it with transactions. To avoid it, you may update one different key every transaction.
Subject: MVCC Error Round 3 - Profile 2org1peergoleveldb
We are getting below error, while trying Caliper version 0.3.0 in round 3.
Could you please advise whether all the transactions should pass and there shouldn’t be any failure.
Please do let me know if more information is required.
Thanks and Regards,
============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy
statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html
internally within TechMahindra. ============================================================================================================================