Jira (PDB-4930) Investigate PG deadlocks with latest_report_id

2020-10-14 Thread Austin Boyd (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Boyd updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4930  
 
 
  Investigate PG deadlocks with latest_report_id   
 

  
 
 
 
 

 
Change By: 
 Austin Boyd  
 
 
Zendesk Ticket Count: 
 1  
 
 
Zendesk Ticket IDs: 
 41188  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374800.160261184.55334.1602663420092%40Atlassian.JIRA.

Jira (PDB-4930) Investigate PG deadlocks with latest_report_id

2020-10-14 Thread Austin Boyd (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Boyd updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4930  
 
 
  Investigate PG deadlocks with latest_report_id   
 

  
 
 
 
 

 
Change By: 
 Austin Boyd  
 
 
Labels: 
 jira_escalated  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374800.160261184.55333.1602663420037%40Atlassian.JIRA.

Jira (PDB-4930) Investigate PG deadlocks with latest_report_id

2020-10-13 Thread Zachary Kent (Jira) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4930  
 
 
  Investigate PG deadlocks with latest_report_id   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/10/13 10:57 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Zachary Kent  
 

  
 
 
 
 

 
 One of our PE customers recently had a few instances of deadlocks that postgres detected in their logs. See below for example    
 
 
 
 
 2020-10-13 04:44:56.786 GMT [db:pe-puppetdb,sess:5f852d78.4f01,pid:20225,vtid:102/1047291,tid:181623009] ERROR:  deadlock detected  
 
 
 2020-10-13 04:44:56.786 GMT [db:pe-puppetdb,sess:5f852d78.4f01,pid:20225,vtid:102/1047291,tid:181623009] DETAIL:  Process 20225 waits for ShareLock on transaction 181623010; blocked by process 21558.  
 
 
 	Process 21558 waits for ShareLock on transaction 181623009; blocked by process 20225.  
 
 
 	Process 20225: UPDATE certnames SET latest_report_id = $1,latest_report_timestamp = $2 WHERE certname = $3AND ( latest_report_timestamp < $4  OR latest_report_timestamp is NULL )  
 
 
 	Process 21558: UPDATE certnames SET latest_report_id =