Jira (PDB-2732) Refactor retry/discard logic for "in-memory" attempts

Ryan Senior (JIRA)

unread,

May 23, 2016, 10:25:04 AM5/23/16

to puppe...@googlegroups.com

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 level can be the normal failure case (i.e. being delayed and reenqueued). Once the threadpools get in place, we will change this to scheduling a thread in memory to retry the message. To do these we need the new threadpool in place (separate ticket) then work to change this 2nd level behavior (separate ticket).