** Description changed:

+ [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::asio::socket_base::max_connections.
  
+ [Test Case]
+ 
+ Add the 'max_connection_backlog' config option to the RGW beast frontend
+ configuration and check that it is ignored and not used.
+ 
+ [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://tracker.ceph.com/issues/43952
+ Upstream PRs:
+ https://github.com/ceph/ceph/pull/33053
+ https://github.com/ceph/ceph/pull/33340
+ https://github.com/ceph/ceph/pull/33341

** Patch added: "train.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1867386/+attachment/5338154/+files/train.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867386

Title:
  Beast frontend does not allow tuning of maximum backlog of pending
  connections

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1867386/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to