yahoo-eng-team team mailing list archive

[Attila Fazekas <afazekas@xxxxxxxxxx>]

Public bug reported:

ml2_vxlan_allocations, ml2_gre_allocations, ml2_vlan_allocations tables
has field named 'allocated'.

These tables  frequently used by similar queries:
SELECT ml2_vxlan_allocations.vxlan_vni AS ml2_vxlan_allocations_vxlan_vni, ml2_vxlan_allocations.allocated AS ml2_vxlan_allocations_allocated FROM ml2_vxlan_allocations WHERE ml2_vxlan_allocations.allocated = 0  LIMIT 1;

This does select without an index, which causes very poor performance.
If Transaction which involved in allocation took long time, in parallel can lead to an allocation failure and retry.

These tables needs to have index on the 'allocated' field.

In the ml2_vlan_allocations table case consider creating an index on
(physical_network, allocation) together.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  ml2_vxlan_allocations, ml2_gre_allocations, ml2_vlan_allocations tables
- has field named 'allocation'.
+ has field named 'allocated'.
  
- These tables  frequently used by similar queries: 
+ These tables  frequently used by similar queries:
  SELECT ml2_vxlan_allocations.vxlan_vni AS ml2_vxlan_allocations_vxlan_vni, ml2_vxlan_allocations.allocated AS ml2_vxlan_allocations_allocated FROM ml2_vxlan_allocations WHERE ml2_vxlan_allocations.allocated = 0  LIMIT 1;
  
  This does select without an index, which causes very poor performance.
  If Transaction which involved in allocation took long time, in parallel can lead to an allocation failure and retry.
  
  These tables needs to have index on the 'allocated' field.
  
  In the ml2_vlan_allocations table case consider creating an index on
  (physical_network, allocation) together.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1412348

Title:
  Missing index on allocated

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  ml2_vxlan_allocations, ml2_gre_allocations, ml2_vlan_allocations
  tables has field named 'allocated'.

  These tables  frequently used by similar queries:
  SELECT ml2_vxlan_allocations.vxlan_vni AS ml2_vxlan_allocations_vxlan_vni, ml2_vxlan_allocations.allocated AS ml2_vxlan_allocations_allocated FROM ml2_vxlan_allocations WHERE ml2_vxlan_allocations.allocated = 0  LIMIT 1;

  This does select without an index, which causes very poor performance.
  If Transaction which involved in allocation took long time, in parallel can lead to an allocation failure and retry.

  These tables needs to have index on the 'allocated' field.

  In the ml2_vlan_allocations table case consider creating an index on
  (physical_network, allocation) together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1412348/+subscriptions