Jira (PDB-2732) Refactor retry/discard logic for "in-memory" attempts
Title: Message Title Claudia Petty updated an issue PuppetDB / PDB-2732 Refactor retry/discard logic for "in-memory" attempts Change By: Claudia Petty Labels: new-feature Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.133223.1464013445000.2487.1687359482129%40Atlassian.JIRA.
Jira (PDB-2732) Refactor retry/discard logic for "in-memory" attempts
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-2732 Refactor retry/discard logic for "in-memory" attempts Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2732) Refactor retry/discard logic for "in-memory" attempts
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2732 Refactor retry/discard logic for "in-memory" attempts Issue Type: New Feature Assignee: Unassigned Created: 2016/05/23 7:24 AM Fix Versions: PDB 4.2.0 Priority: Normal Reporter: Ryan Senior Currently, PDB failures get enqueued into the "scheduler" queue and get resubmitted to the regular queue after some amount of time has passed. Instead, the flow should be as follows Upon failure, the message is retried in-memory 10* times After 10* failures, the message progresses to 2nd level failure Message is retried 10* times for each 2nd level failure After 5* 2nd level failures, progresses to 3rd level 3rd level, the message is discarded, i.e. DLQ Any number that has a '*' by it means it should be configurable. For now, second