High Rate of Lost Events about clip

[asmuth]

Hey, sorry for the late answer. The "oops, lost an event" message is actually a bit misleading right now. It means, that an event-id was popped from the queue but no hash with the accompanying "#{prefix}-event-#{event_id}" key was found.

After a restart this may be cause by expired data - Incoming events have a ttl of 2 minutes per default (see opts[:event_queue_ttl]).

Are you submitting the events directly into the redis queue?

[arctica]

It means, that an event-id was popped from the queue but no hash with the accompanying "#{prefix}-event-#{event_id}" key was found.

This sounds like the race condition that I just reported (issue #14).

[asmuth]

I guess this was fixed in issue #14