Kolla should be able to handle connection limit for database according to infra

Bug #1564008 reported by Manjeet Singh Bhatia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Wishlist
Unassigned

Bug Description

while deploying kolla fails to calculate connection limit for particular setup.

use case: I was using kolla on 50 nodes it had issues with database connection limit
for 1000 vms which I have set manually in mariadb and re deploy kolla. I think it will be
good if kolla can calculate it before hand and set it while deployement

Tags: retriage
Revision history for this message
Hui Kang (huikang27) wrote :

Hi, manjeet very nice idea. Could you post the error message you saw, as well as the command you run to fix that? Thanks. - Hui

Revision history for this message
Steven Dake (sdake) wrote :

I think adding calculation logic complicates the deployment significantly and doesn't account for situations in which additional scaling occurs (such as adding compute or storage nodes). This is a feature request rather then a bug. The bug you ran into has been fixed in master and stable/mitaka and you should no longer run into database limits on our target scale limits out of the box (100 node cluster with 3 controller nodes, 10 storage nodes, 87 compute nodes under full load).

Changed in kolla:
importance: Undecided → Wishlist
milestone: none → newton-1
status: New → Triaged
Changed in kolla:
milestone: newton-1 → newton-2
tags: added: retriage
Changed in kolla:
milestone: newton-2 → newton-3
Changed in kolla:
milestone: newton-3 → occata-1
Changed in kolla:
milestone: ocata-1 → ocata-2
Changed in kolla:
milestone: ocata-2 → ocata-3
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :
Changed in kolla:
status: Triaged → Fix Released
MarginHu (margin2017)
summary:
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.