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

Add experimental cache self-monitoring #4529

Closed
wants to merge 1 commit into from

Conversation

rob05c
Copy link
Member

@rob05c rob05c commented Mar 23, 2020

Adds an experimental Proof-of-Concept project to replace the Cache Health Monitoring part of Traffic Monitor with cache remap rules, so the caches monitor themselves.

This has a number of benefits.

  • saves TC operators having to deploy a CPU- and network-intensive application.
  • saves the TC project the difficult and expensive development of a high-performance application.
  • Automatically horizontally scalable, solves the current monitor scalability problem out of the box.

In a nutshell, there are 3 components:

  • astatstwo replaces astats, monitors health on the cache, and returns a 204 or 503.
  • remapgen generates remap rules for any cache to forward health requests to any other cache.
    • will include remaps for near, far, IPv4, and IPv6 health.
  • healthcombiner requests the health of all caches from localhost and builds /CRStates.json consumed by Traffic Router.
    • Not strictly necessary, the Router could request health for each cache, but this allows us to avoid modifying the Router.

See the README.md for more details.

No tests, no docs, no changelog, experimental PoC.

  • This PR is not related to any other Issue

Which Traffic Control components are affected by this PR?

None, experimental.

What is the best way to verify this PR?

Follow the instructions in the README.md to create the experimental setup.

If this is a bug fix, what versions of Traffic Control are affected?

Not a bug fix.

The following criteria are ALL met by this PR

  • This PR includes tests OR I have explained why tests are unnecessary
  • This PR includes documentation OR I have explained why documentation is unnecessary
  • This PR includes an update to CHANGELOG.md OR such an update is not necessary
  • This PR includes any and all required license headers
  • This PR ensures that database migration sequence is correct OR this PR does not include a database migration
  • This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

@rob05c rob05c added the experimental a feature/component not directly supported by ATC label Mar 23, 2020
@rob05c rob05c closed this Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned experimental a feature/component not directly supported by ATC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants