Actually run the distributed tx expiry task #10297
Merged
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.
What does this PR do?
Actually create a timer and schedule the distributed transaction timeout task.
The
com.orientechnologies.orient.server.distributed.impl.ODistributedDatabaseImpl#startTxTimeoutTimerTask
method creates the timeout task, but never schedules it on a Timer.Motivation
During heap dump analysis we observed some transactions remaining in the tracking list forever.
Related issues
Additional Notes
Checklist
[x] I have run the build using
mvn clean package
command[] My unit tests cover both failure and success scenarios