Fix TM issue where CRConfig is never updated #6748
Merged
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.
PR #6625 reduced the TM dependency on CRConfig data, but it accidentally
caused TM to no longer poll for new CRConfig snapshots. This adds the
CRConfig request back into the polling loop so that it updates its
in-memory copy for internal use (if necessary) and for serving to TR.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Start TM, then take a new snapshot, and ensure that TM updates its crconfig.backup file with the new snapshot and serves the new snapshot via its
/publish/CrConfig
endpoint.If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist