utilizing mongodb TTL feature #49
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- reducing history in the database for 30 days instead of 90 days. - added new index in the mongodb to activate TTL feature for faster process of cleaning finished jobs after 7 days.
completeTime is no longer part of latestTime to avoid invalid date records after changed to mongodb TTL and completeTime field to datetime type.
making it more satisfying by increase the mongodb TTL to 30 days before deleting the old finished jobs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's faster and easier to rely on mongodb TTL feature to clean the old finished jobs after 30 days.
This update is changing the format how we save the completeTime value in the database of ScriptTask.
Also it adds a new index to the database to activate the TTL feature to clean finished jobs older than 30 days. Because of this index addition it will cause re-indexing of the ScriptTask db when update (no data lose at all, but it's a good thing to backup database before updating).