Add FV and Blobs not cleaned up on failed transactions in query handle #189
Labels
Bug
Indicates unexpected or undesired behaviors
Priority: Backlog
Tasks that are not pressing, but to be tracked and revisited
Describe the bug
Currently the query cleanup logic PMGD query handling class does not include removal of stored FVs and blobs for failed transactions, meaning there is a risk of space leakage when a VDMS transaction is rolled back.
To Reproduce
Difficult to deterministically reproduce at it requires a transaction failure at the database level for PMGD, however the internal logic does not account for FV or Blob removal so its an obvious risk point.
Expected behavior
In the event an internal error that triggers a rollback, the written data should also be removed.
Currently this is an unlikely case, but we should not lose track of it.
The text was updated successfully, but these errors were encountered: