fix(cairo): fix scoreboard race for new table readers #1811
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refs: #1559
Fresh table reader instances were using 0 transaction numbers in scoreboard acquire/release calls which led to races in the scoreboard's min value initialization. The init() method in scoreboard was swapping 0 min value with L_MIN and a later table reader was swapping this L_MIN value with its current transaction number. This could have led to min being set to a value greater than 0 while there are some fresh reader instances that haven't released their txn 0 yet. As the result of this race, the assertion in releaseTxn() was failing.
To fix this race, the TxnScoreboard Java class now adds 1 to all received txn values before calling the C++ implementation.