Ah, I found a change to the my.cnf that was done for other purposes on the
cluster, I had been running with a standard issue one before.
Thanks for the pointers!
Ruth
From: LEIBOVICI Thomas <[email protected]<mailto:[email protected]>>
Organization: CEA-DAM
Date: Thursday, April 17, 2014 at 1:53 AM
To: Ruth Klundt <[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [EXTERNAL] Re: [robinhood-support] db errors
Hi Ruth,
I found the following info about this error on MySQL forums:
This:
If you are not planning to use your MySQL server for the replication consider
turning the binary logging off by removing the option --log-bin from the
command options for the mysqld utility starting the MySQL server.
And this:
To change to row based binary logging, set the following in /etc/my.cnf (or
your my.cnf if it's elsewhere):
binlog_format=row
Do you have specific tunings in your /etc/my.cnf? or a specific DB architecture
(distributed / replicated)?
What MySQL implementation do you use? Oracle Enterprise, Oracle GPL, MariaDB?
I hope this helps,
Thomas
On 04/16/14 18:03, Klundt, Ruth wrote:
Transaction
level 'READ-COMMITTED' in InnoDB is not safe for binlog mode
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
