Jira (PDB-3224) Add the ability to stop processing different types of commands via API

[Nick Walker (JIRA)]

Nick Walker created an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API Issue Type: New Feature Assignee: Unassigned Created: 2016/12/12 8:07 AM Labels: tcse Priority: Normal Reporter: Nick Walker 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. Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Nick Walker (JIRA)]

Nick Walker updated an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API

Change By: Nick Walker h1.  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.

h1.  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.

Add Comment

[Ryan Senior (JIRA)]

Ryan Senior updated an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API

Change By: Ryan Senior Sprint: Hopper

Add Comment

[Ryan Senior (JIRA)]

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API

Change By: Russell Mull Sprint: Hopper

Add Comment

[Russell Mull (JIRA)]

[Nick Walker (JIRA)]

Nick Walker updated an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API

Change By: Nick Walker CS Priority: Needs Priority

Add Comment

This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

[Owen Rodabaugh (JIRA)]

Owen Rodabaugh updated an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API

Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: 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. CS Severity: 3 - Serious CS Business Value: 4 - $$$$$ CS Frequency: 2 - 5-25% of Customers

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

PuppetDB / PDB-3224 Add the ability to stop processing different types of commands via API

Change By: Claudia Petty Labels: new-feature tcse

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)