Warn when back_log is set higher than net.core.somaxconn
Bug #1103509 reported by
Raghavendra D Prabhu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.1 |
Won't Fix
|
Medium
|
Unassigned | |||
| 5.5 |
Triaged
|
Medium
|
Unassigned | |||
| 5.6 |
Triaged
|
Medium
|
Unassigned | |||
| 5.7 |
Triaged
|
Medium
|
Unassigned | |||
Bug Description
The back_log parameter used for setting the length of listen
queue, however its value is implementation bound by
net.core.somaxconn (which is defined by default to be 128).
So, setting a value of back_log to say, 2048 when
net.core.somaxconn is at default 128 has no effect.
It would be better to emit a warning to error log in this case.
| summary: |
- Warn when back_log is set lower than net.core.somaxconn + Warn when back_log is set higher than net.core.somaxconn |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #1 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Raghu -
This is applies to the upstream as well, doesn't it? Can you please report it there and link the report?