See, for example:
Here's an example of what I can happen (would probably be good to write up a test case for each read/update):
Concurrent update via increment and put.
The put grabs the row lock first and updates the memstore, but releases the row lock before the MVCC is advanced. Then, the increment grabs the row lock and reads right away, reading the old value and incrementing based on that.
There are a few options here:
1) Waiting for the MVCC to advance for read/updates: the downside is that you have to wait for updates on other rows.
2) Have an MVCC per-row (table configuration): this avoids the unnecessary contention of 1)
3) Transform the read/updates to write-only with rollup on read.. E.g. an increment would just have the number of values to increment.
|Add test that increment/append properly integrate with MVCC||Closed||Unassigned|
|Test for: CheckAndPut should properly read MVCC||Closed|
|Add a test that append is atomic||Closed||Unassigned|