Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order Manager: Split deletion of obsolete orders into multiple transactions #183

Closed
tangobravo62 opened this issue Jan 17, 2023 · 2 comments
Labels
design change Change or removal of existing features implemented Issue has been implemented and is ready for test

Comments

@tangobravo62
Copy link
Collaborator

Closed orders are deleted automatically once they reach their defined eviction time (if any). Currently all orders found in one run of the cleanup thread (in class CleanupOrdersThread) are deleted in a single transaction. This shall be changed to one transaction per order, as order deletion may be time-consuming (depending on the number of job steps).

@tangobravo62 tangobravo62 added the design change Change or removal of existing features label Jan 17, 2023
tangobravo62 added a commit that referenced this issue Jan 31, 2023
... and check for unset mandatory attributes corrected in create and
modify
@tangobravo62
Copy link
Collaborator Author

Change performed and tested locally.

@tangobravo62 tangobravo62 added the implemented Issue has been implemented and is ready for test label Jan 31, 2023
@tangobravo62
Copy link
Collaborator Author

Order deletion worked without problems on Sentinel-1 Systematic Production environment for one year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design change Change or removal of existing features implemented Issue has been implemented and is ready for test
Projects
None yet
Development

No branches or pull requests

1 participant