Beast frontend does not allow tuning of maximum backlog of pending connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Medium
|
Unassigned | ||
Stein |
Fix Released
|
Medium
|
Unassigned | ||
Train |
Fix Released
|
Medium
|
Unassigned | ||
Ussuri |
Fix Released
|
Medium
|
Unassigned | ||
ceph (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Medium
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned |
Bug Description
[Impact]
Currently, RGW has no option to configure the maximum size for the queue of connections waiting to be accepted when using the Beast frontend. Instead, it uses the value from boost::
[Test Case]
Add the 'max_connection
[Regression Potential]
This change has been reviewed upstream and have been passed through the usual upstream ceph QA tests.
[Other info]
This bug is similar to 1838109, which reports the same issue but for the civetweb frontend.
Ceph tracker bug: https:/
Upstream PRs:
https:/
https:/
https:/
tags: | added: sts-sru-needed |
Changed in ceph (Ubuntu Disco): | |
status: | New → Won't Fix |
This is already fixed upstream:
https:/ /github. com/ceph/ ceph/pull/ 33053 /github. com/ceph/ ceph/pull/ 33340 /github. com/ceph/ ceph/pull/ 33341
https:/
https:/