# Expected Diagnosis: sustained-node-memory-pressure-during-transaction-workload

The expected result should converge on the case-specific mechanism below while
keeping conclusions bounded by the collected evidence.

## Expected conclusion

TiKV v7.5.6 leaked transaction-lock-related memory when Async Commit or 1PC overlapped with concurrent range scans. The retained state accumulated in ConcurrencyManager or LockTable. Disabling Async Commit/1PC prevents new leakage, restart clears already leaked memory, and upgrading to v7.5.8 or later provides the fix.

## Required evidence chain

- Show sustained TiKV memory growth that is not explained by normal cache behavior or a short workload burst.
- Identify the version-specific interaction between Async Commit/1PC and concurrent range scans that retains transaction lock state.
- Recommend disabling Async Commit/1PC to stop new leakage and restarting affected TiKV nodes to clear existing retained state.
- Recommend upgrading to v7.5.8 or later for the durable fix.