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

Command Queue Grows Steadily Over Time not related to load

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 5.1.5, PDB 5.2.1
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Data Platform
    • Story Points:
      1
    • Sprint:
      Data Platform 2018-03-14
    • Method Found:
      Customer Feedback
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      PuppetDB now correctly reduces the command queue size when a malformed message is submitted to the queue. Previously if you submitted a message that PuppetDB discards, the command queue would increase when the message came in and would not reduce when the message was discarded.
      Show
      PuppetDB now correctly reduces the command queue size when a malformed message is submitted to the queue. Previously if you submitted a message that PuppetDB discards, the command queue would increase when the message came in and would not reduce when the message was discarded.
    • QA Risk Assessment:
      Needs Assessment

      Description

       The Problem

      Over time we notice that the queue depth grows just a little bit and never drops back down.  Over the course of a few days it'll be sitting around 300-400 despite capacity to work it down.  

      After graphing some other metrics we see that discard count seems suspiciously close to the command queue which grows over time.

      I suspect that discards are not correctly removed from the counter for queue depth.

       
       

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  rob.browning Rob Browning
                  Reporter:
                  nick.walker Nick Walker
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support