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

Add the ability to stop processing different types of commands via API

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Normal
    • Resolution: Won't Do
    • None
    • None
    • PuppetDB
    • Normal
    • 2 - 5-25% of Customers
    • 3 - Serious
    • 4 - $$$$$
    • Hide
      This would reduce the impact of performing maintenance because it would only take down the portion of the API that hits the tables that maintenance is running against. Once maintenance is complete the command queue would be able to work through it's backlog.
      Show
      This would reduce the impact of performing maintenance because it would only take down the portion of the API that hits the tables that maintenance is running against. Once maintenance is complete the command queue would be able to work through it's backlog.
    • Needs Assessment

    Description

      The Use Case

      I'd like to REBUILD some indexes or VACUUM FULL a table but when I do the PuppetDB service continues trying to write changes to the table.

      I'd like to run PuppetDB GC via the api and when I do, stop processing the type of command I'm cleaning up to reduce contention on the database.

      Thoughts

      I think the GC case is an added benefit but probably not enough of a win to warrant this feature. The real benefit comes from being able to allow database maintenance while the service stays up and queues the incoming commands.

      If I don't process facts while I'm performing a blocking operation on one of the facts tables that means that I can still keep my commands / sec up by processing reports instead of lowering my throughput with lots of failed commands on facts. This means I keep the queue lower overall during a maintenance period.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nick.walker Nick Walker
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support