No way to increase haproxy maxconn

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

Bug Description

Hi,

There currently is no way to increase global or defaults maxconn, so we're stuck at 2000.
I wonder if this should be a config option (same value for both), 2 config options (1 for each), or if we should do some "clever" computation from the nginx worker_connections & worker_processes.

Thanks

Related branches

Haw Loeung (hloeung)
Changed in content-cache-charm:
status: New → Triaged
importance: Undecided → High
Haw Loeung (hloeung)
Changed in content-cache-charm:
assignee: nobody → Haw Loeung (hloeung)
Haw Loeung (hloeung)
Changed in content-cache-charm:
status: Triaged → In Progress
Revision history for this message
Haw Loeung (hloeung) wrote :

Landed a change to expose configuring HAProxy's maxconns. Also bumped it from the Ubuntu default of 2000 to 8192.

Will work on changes to auto calculate this (likely based on nbthreads/CPU cores or something else).

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.