Hide Forgot
Description of problem: API LB uses the default value of maximum concurrent connections which is 2K, this value should be increased. Version-Release number of selected component (if applicable): 42.80.20190827.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to Yossi Boaron from comment #0) > Description of problem: > API LB uses the default value of maximum concurrent connections which is 2K, > this value should be increased. > > Version-Release number of selected component (if applicable): > 42.80.20190827.1 > > How reproducible: > > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info: Thank you for this bug but you could have at the very least provided more information on how the MCO is in charge of this? steps to reproduce perhaps? I don't have any clue about how a team is supposed to tackle a bug reported like this. It's literally missing everything, and we have a template for a reason for reporter to fill.
I cannot see how, from the very few lines of this bug, the MCO could be in charge of the API LB (assuming that stands for API LoadBalancer)
Ok, I"m now seeing the PR in MCO
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922