This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Fix maxmind database update and reload#6029
Merged
rob05c merged 1 commit intoapache:masterfrom Jul 19, 2021
ezelkow1:t3c-mmdb-gz
Merged
Fix maxmind database update and reload#6029rob05c merged 1 commit intoapache:masterfrom ezelkow1:t3c-mmdb-gz
rob05c merged 1 commit intoapache:masterfrom
ezelkow1:t3c-mmdb-gz
Conversation
The plugin and database update do not play nicely when updating via a copy. This change uses a temporary database and a move to make it atomic, then does a touch and reload on remap.config in order to reload the plugin with the new database.
jrushford
approved these changes
Jul 16, 2021
rob05c
approved these changes
Jul 19, 2021
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The plugin and database update do not play nicely when updating via a copy. This change uses a temporary database and a move to make it atomic, then does a touch and reload on remap.config in order to reload the plugin with the new database.
What does this PR (Pull Request) do?
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Set the date back on a maxmind database on a cache. Run t3c and verify that it updates as it should and that an ATS reload is initiated
If this is a bug fix, what versions of Traffic Control are affected?
The following criteria are ALL met by this PR
Additional Information