This has been added to the accounting web page. Thanks for the note. I
agree with the frustration of MySQL just chirping right along, no error
is even given when we specifically set the engine to InnoDB. Hopefully
this has only bitten a couple of people, and hopefully the documentation
update will help others.
Danny
On 06/27/2014 01:31 PM, Kevin M. Hildebrand wrote:
I might have missed it, but I didn't see any place in the SLURM
install docs that mention that InnoDB is a requirement when using MySQL.
I've just spent a couple of hours debugging why when using sacctmgr,
answering "no" to any of the commit questions is the same as answering
"yes".
It turns out that my MySQL default engine is MyISAM, which doesn't
support transactions, so rollbacks on "no" responses don't work.
The most frustrating part is that MySQL runs along happily without any
warnings to tell you that all of the transaction controls are being
ignored.
So, I'd suggest adding a warning to the install docs that InnoDB is
required and must be the default when the tables are initially created.
Thanks!
Kevin
--
Kevin Hildebrand
Division of IT
University of Maryland, College Park
