Fabric Will Reject Transactions That Update the Same World State Key
Fleeting- External reference: https://stackoverflow.com/questions/45347439/mvcc-read-conflict-when-submitting-multiple-transactions-concurrently
Hyperledger’s Fabric - MVCC_READ_CONFLICT when submitting multiple transactions concurrently - Stack Overflow
If you have multiple threads updating a given key concurrently then you will hit MVCC read conflict issues, as there is no global lock to prevent concurrent updates to a key. At commit time the version number of the key is checked – if it is different from that which was previously read then the transaction is rolled back (because the prior read is now dirty)
To be understood: Concurently reading and writing to the world state on the same key will result on the rejection of one transaction. This means that you need to catch the rejection and try again later.