← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1564648] Re: nova notifier should send first event immediately

 

Reviewed:  https://review.openstack.org/300245
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=255e8a839db0be10c98b5d9f480ce476e2f2e171
Submitter: Jenkins
Branch:    master

commit 255e8a839db0be10c98b5d9f480ce476e2f2e171
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Thu Mar 31 05:03:12 2016 -0700

    Turn nova notifier into a proper rate limiter
    
    This adjusts the batching logic in the Nova notifier to immediately
    send and then sleep to allow batching of subsequent calls in the batch
    interval.
    
    So rather than always wait for 2 seconds to elapse while batching,
    batching will only occur in the 2 second period after a call is made.
    This turns the batch notifier into a standard queuing rate limiter.
    
    The upside to this is a single port create results in an immediate
    notification to Nova without a delay.
    
    The downside is now that a sudden burst of 6 port creations to a
    previously idle server will result in 2 notification calls to Nova
    (1 for the first call and another for the other 5).
    
    Closes-Bug: #1564648
    Change-Id: I82f403441564955345f47877151e0c457712dd2f


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  nova notifier should send first event immediately

Status in neutron:
  Fix Released

Bug description:
  The nova batch notifier currently waits to batch up events on every
  single notification. This means even in a quiet system, the batching
  mechanism will add a delay to every single notification to Nova. This
  extra 2 seconds (or whatever it is configured to) builds up over time
  and adds quite a bit of delay to tempest runs (2 seconds * number of
  booted VMs).

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


References