Better health checks for the caching layer
Bug #1891262 reported by
Haw Loeung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Content Cache Charm |
Fix Released
|
High
|
Haw Loeung | ||
Bug Description
Hi,
The charm configures HAProxy to use the same health checks for both backends and the caching layer itself. These are usually not caching. It should instead set up some kind of health check location within the caching layer (nginx currently) and HAProxy check that. Or maybe that the port is up and that's all.
Related branches
~hloeung/content-cache-charm:tuning
- James Simpson: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 771 lines (+111/-62)26 files modifiedreactive/content_cache.py (+9/-8)
templates/nginx_cfg.tmpl (+3/-0)
tests/unit/files/content_cache_rendered_haproxy_test_output.txt (+10/-10)
tests/unit/files/content_cache_rendered_haproxy_test_output2.txt (+1/-1)
tests/unit/files/content_cache_rendered_haproxy_test_output3.txt (+1/-1)
tests/unit/files/content_cache_rendered_haproxy_test_output_auto_maxconns.txt (+10/-10)
tests/unit/files/content_cache_rendered_haproxy_test_output_backup.txt (+1/-1)
tests/unit/files/content_cache_rendered_haproxy_test_output_load_balancing_algorithm.txt (+10/-10)
tests/unit/files/content_cache_rendered_haproxy_test_output_processes_and_threads.txt (+10/-10)
tests/unit/files/content_cache_rendered_haproxy_test_output_processes_and_threads_haproxy2.txt (+10/-10)
tests/unit/files/content_cache_rendered_haproxy_test_output_srv_template.txt (+1/-1)
tests/unit/files/nginx_config_rendered_test_output-basic_site.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-reuseport.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site1.local-secrets.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site1.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site10.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site11.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site2.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site3.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site4.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site5.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site6.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site7.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site8.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-site9.local.txt (+3/-0)
tests/unit/files/nginx_config_rendered_test_output-token_site.txt (+3/-0)
| Changed in content-cache-charm: | |
| status: | New → In Progress |
| importance: | Undecided → Low |
| importance: | Low → Medium |
| assignee: | nobody → Haw Loeung (hloeung) |
Revision history for this message
| Haw Loeung (hloeung) wrote | #1 |
Revision history for this message
| Haw Loeung (hloeung) wrote | #2 |
| Changed in content-cache-charm: | |
| importance: | Medium → High |
| Changed in content-cache-charm: | |
| status: | In Progress → Fix Committed |
| Changed in content-cache-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Could be done with Nginx' stub_status[1].
[1]http://