Issue #7199 has been updated by Jason Smith.
What is the status of this bug? We are trying to use the inventory service on our puppet system with a little over 1,000 nodes in our cluster and it seems even worse that originally described in this bug report. Besides the initial puppet run that produced a lot of MySQL deadlock errors, we are also seeing frequent MySQL has gone away errors on subsequent puppet runs, like: Mysql::Error: MySQL server has gone away: UPDATE `inventory_nodes` SET `timestamp` = '2011-10-25 13:31:14', `updated_at` = '2011-10-25 13:31:14' WHERE `id` = 598 We also have storeconfigs enabled with the puppet queue daemon and the ActiveMQ stomp daemon running. Does the inventory service also make use of this asynchronous DB updating? We are running the latest 2.6.x puppet server on RHEL5. ---------------------------------------- Bug #7199: Mysql deadlock with inventory enabled https://projects.puppetlabs.com/issues/7199 Author: Chad Huneycutt Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: I just enabled the new inventory features with the activerecord terminus, and I am seeing errors like the following in my master.log: Mysql::Error: Deadlock found when trying to get lock; try restarting transaction: INSERT INTO `inventory_facts` (`value`, `name`, `node_id`) VALUES ('Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz', 'processor3', 29) If that seems serious I can track down more info; I see it relatively frequently. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
