Cannot set maxconn for sites that don't have a backend

Bug #2015989 reported by Junien F
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Content Cache Charm
Fix Released
High
Haw Loeung

Bug Description

Hi,

If a site is serving local files (such as esm.ubuntu.com), it appears that with the current charm code, it's not possible to configure its maxconn, which will stay at a hardcoded value of 200 [1].

This is a problem, especially because a site service local files should be able to manage quite more than that.

Thanks

[1] The "continue" at https://git.launchpad.net/content-cache-charm/tree/reactive/content_cache.py?id=2d4a14b89bcc54f23f067b95a5dd53f084f6ff46#n320 is before "backend-maxconn" gets considered at https://git.launchpad.net/content-cache-charm/tree/reactive/content_cache.py?id=2d4a14b89bcc54f23f067b95a5dd53f084f6ff46#n341 so the default value from https://git.launchpad.net/content-cache-charm/tree/lib/haproxy.py?id=2d4a14b89bcc54f23f067b95a5dd53f084f6ff46#n261 is used.

Related branches

Haw Loeung (hloeung)
Changed in content-cache-charm:
status: New → In Progress
assignee: nobody → Haw Loeung (hloeung)
importance: Undecided → High
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: In Progress → Fix Committed
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.