Improve the limbo transactions scan at the end of the sweep [CORE3994] #4326
Labels
affect-version: 2.0.5
affect-version: 2.0.6
affect-version: 2.0.7
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.1.3
affect-version: 2.1.4
affect-version: 2.1.5
affect-version: 2.5.0
affect-version: 2.5.1
affect-version: 2.5.2
affect-version: 3.0 Initial
component: engine
fix-version: 2.5.3
fix-version: 3.0 Alpha 1
priority: minor
qa: cannot be tested
type: improvement
Submitted by: @dyemanov
Is related to CORE3908
Votes: 1
After performing a garbage collection pass, the sweep advances the global OIT number. But it cannot be advanced further than the oldest known in-limbo transaction. In order to find one, the engine scans all the transactions since the old OIT. But the used algorithm has a quadratic cost, so it looks like a server hang if the transaction gap is big enough. See CORE3908 for the test details.
Commits: 361c5a3 87c6573
The text was updated successfully, but these errors were encountered: