Thanks for looking into this Michael. Only allowing one external event every 30 seconds seems like kind of a high initial setting. However, I've put in a workaround on our side that will retry sending the event after 30 seconds and queue the rest if an error is received while logging.
-Chris > -----Original Message----- > From: Michael Pasternak [mailto:mpast...@redhat.com] > Sent: Monday, September 23, 2013 6:36 AM > To: Eli Mesika > Cc: Morrissey, Christopher; engine-devel@ovirt.org > Subject: Re: [Engine-devel] External events and flood rate > > Eli, > > any reason for hardcoding this [1]? i'd move it to vdc_config. > > [1] Math.max(auditLogable.getEventFloodInSec(), 30) // Min duration for > External Events is 30 sec > > On 09/19/2013 12:50 AM, Morrissey, Christopher wrote: > > Hi All, > > > > > > > > I've been working on submitting external events to oVirt through the > > REST API. It seems to be working in general, although it appears that, > > no matter what value I put for the flood rate in the event, only 1 or > > so events are allowed every 30 seconds. If I send another event during this > time, I get an operation failed exception. Should the flood rate have any > impact on this? Is there any way to allow my code to get an event through > when needed or should I have a thread that shoots them off every 30 > seconds if several occur too quickly together? > > > > > > > > -Chris > > > > > > > > *Chris Morrissey* > > > > Software Engineer > > > > NetApp Inc. > > > > 919.476.4428 > > > > > > > > > > > > _______________________________________________ > > Engine-devel mailing list > > Engine-devel@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > -- > > Michael Pasternak > RedHat, ENG-Virtualization R&D _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
