On Tue, Jan 3, 2012 at 2:58 PM, Daniel Pittman <[email protected]>wrote:
> On Tue, Jan 3, 2012 at 14:52, Russell Van Tassell <[email protected]> > wrote: > > > Mysql::Error: The total number of locks exceeds the lock table size: > ALTER > > TABLE resource_events ADD CONSTRAINT > fk_resource_events_resource_status_id > > FOREIGN KEY (resource_status_id) REFERENCES resource_statuses(id) ON > DELETE > > CASCADE; > > Wow. I don't think I have seen a "total number of locks too big" > error before. You need to tune MySQL to have a bigger lock table size > for this to work. On the plus side, once you do that, run the > migration thing again and it should pick up from where it left off. > > Yeah, I've tried re-running it already, and now it's breaking on something else... (BTW, it doesn't actually pick up where it left off ... it still re-runs the deletes - though they run a little bit faster ,now) -- begin -- execute("ALTER TABLE reports ADD CONSTRAINT fk_reports_node_id FOREIGN KEY (node_id) REFERENCES nodes(id) ON DELETE CASCADE;") rake aborted! An error has occurred, all later migrations canceled: Mysql::Error: Can't create table 'puppet_dashboard.#sql-78e_f3d' (errno: 121): ALTER TABLE reports ADD CONSTRAINT fk_reports_node_id FOREIGN KEY (node_id) REFERENCES nodes(id) ON DELETE CASCADE; Tasks: TOP => db:migrate (See full trace by running task with --trace) -- end -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
