Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delay agent skipping events #2438

Open
crazycaveman opened this issue Dec 12, 2018 · 3 comments
Open

Delay agent skipping events #2438

crazycaveman opened this issue Dec 12, 2018 · 3 comments

Comments

@crazycaveman
Copy link

I'm having some trouble with the delay agent. I'm using that to rate limit how many requests are sent to a webhook at once (5 at a time with an interval of 2 minutes). Sometimes, the same number of events in do not get emitted from the delay agent to the post agent (see screenshot). Is there a way to figure out why this is failing intermittently? TBH, I haven't kept a close eye on it and just noticed it again today. Re-emitting a skipped event causes it to process correctly.

Screenshot and agent configs:
image

  • Delay agent:
{
  "expected_receive_period_in_days": "3",
  "max_events": "500",
  "keep": "newest",
  "max_emitted_events": "5"
}
@dsander
Copy link
Collaborator

dsander commented Dec 13, 2018

Are you using multiple delayed_job background processors? I think it is possible that an Event is dropped when the Agent is ran simultaneously on two processors. If that is the case the root cause would be similar to #2389

@TheChrisK
Copy link

Hi, I manage the installation that @crazycaveman is referring to.

Yes, we are using multiple delayed_job processes, 8 total. The VM has 4c and 4GB of RAM running on Ubuntu 16.04.5.

Was there a config change that resolved the other issue or just a different way of building the agent?

@dsander
Copy link
Collaborator

dsander commented Dec 19, 2018

I think the only way to resolve the issue is to introduce a lock that ensures that Agents which modify the memory do not run on two different delayed job processes at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants