Jira (PDB-4444) PuppetDB never finishes migrating resource_events

[Luke Bigum (JIRA)]

Title: Message Title

Luke Bigum created an issue   PuppetDB / PDB-4444 PuppetDB never finishes migrating resource_events Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2019/06/26 2:58 AM Priority: Normal Reporter: Luke Bigum In our environment, a PuppetDB upgrade never completes - any schema migrations that touch `resource_events` always take too long (over 12+ hours).  The PuppetDB JVM either crashes OOM, or I give up, kill it, and truncate `resource_events` and start it again. This is the migration query that is running: INSERT INTO resource_events_transform ( new_value, corrective_change, property, file, report_id, event_hash, old_value, containing_class, certname_id, line, resource_type, status, resource_title, timestamp, containment_path, message ) VALUES ( $1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16 )+ I'm not sure there's any way to solve this... `resource_events` is by far the largest table, usually around 3-5 million rows.  I've already disabled report processing on our Dev infrastructure to limit the amount of reports stored. Any suggestions, or should I make it practice to truncate this table before every package upgrade? Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314156.1561543112000.61419.1561543140439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.