Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-2865

Implement a quicker "inner loop" retry of commands

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 4.2.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      3

      Description

      Current versions of PuppetDB incur a high cost when a command is retried. The command gets written to a scheduler queue, then re-enqueued in the regular queue, then reprocessed. A very common case is a database transaction issue, where two commands are attempting to update the same data. One thread wins, one loses and has to be retried. We should implement a quicker "inner loop" retry, where we don't incur the I/O overhead in this common case. When the quick retries fail, we can then go through the normal retry logic.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ryan.senior Ryan Senior
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: