Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Implement multisignature pool cleanup #176

Closed
Tracked by #44
sridharmeganathan opened this issue Nov 2, 2020 · 0 comments · Fixed by #846
Closed
Tracked by #44

Implement multisignature pool cleanup #176

sridharmeganathan opened this issue Nov 2, 2020 · 0 comments · Fixed by #846
Assignees
Milestone

Comments

@sridharmeganathan
Copy link
Contributor

sridharmeganathan commented Nov 2, 2020

Description

Make sure the database is purged from invalid transactions. If the transaction is not able to be processed anymore (i.e. it fails on validation), it should be removed from the database after 28 days.

In order to achieve this create two jobs described below.

Motivation

To keep disk space utilisation under control, expired transactions should be removed from the transaction pool.

Acceptance Criteria

  • Expired transactions are being removed after 29 days.
  • Rejected transactions are being removed after 29 days.

Additional Information

Job specification

multisig.cleanup.expired

Job: Clean up expired transactions

This job searches for transactions with expiration dates older than the current timestamp + 29 days and removes them from the database.

multisig.cleanup.rejected

Job: Clean up rejected transactions

This job searches for transactions with rejected = true and modification time older than the current timestamp + 29 days and removes them from the database.

Those transactions are removed from the database.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants