LBV2: when the number of listeners is large, count method of quota executes very slow

Bug #1437996 reported by KaiLin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Expired
Medium
Unassigned

Bug Description

when I created 800+ listeners, it will take about 1 minute to create a new listener.
CAUSE: the count method of quota implement slow since get_listeners_count in lb plugin is not implemented, so it will get the list of all listeners.
The same problem with loadbalancer, pool and healthmonitor.

Tags: lbaas
KaiLin (linkai3)
Changed in neutron:
assignee: nobody → KaiLin (linkai3)
summary: - LBV2: when the number of listeners and loabalaners is big, large, count
- method of quota implement very slow
+ LBV2: when the number of listeners is big, large, count method of quota
+ executes very slow
summary: - LBV2: when the number of listeners is big, large, count method of quota
+ LBV2: when the number of listeners is large, count method of quota
executes very slow
description: updated
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

That's quite strange that list operation is taking 1 minute.

Changed in neutron:
importance: Undecided → Medium
status: New → Confirmed
tags: added: lbaas
Revision history for this message
hgangwx (hgangwx) wrote :

Even iam also seeing this issue. After creation of listeners more than 600+ , its taking more time :3 listeners / min

Revision history for this message
hgangwx (hgangwx) wrote :

seeing the exact issue after 700 + listeners , taking one minute time to create a single listener.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: KaiLin (linkai3) → nobody
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
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.