Luis,
How large is your database? Have you checked for an increase in write
activity on the master leading up to this? Are you running a backup against
the replica?
Thank you,
Tyler
Sent from my Droid Bionic
On Oct 23, 2011 5:40 AM, Luis Motta Campos luismottacam...@yahoo.co.uk
wrote:
Fellow
Dennis,
The following closely simulates the default INTO OUTFILE, you'll have
to modify it slightly for your purposes:
mysql --delimiter=comma -N select_statement.sql \
| sed 's/\/\\\/g' \
| sed 's/\t/\,\/g' \
| sed 's/$/\/g' \
| sed 's/^/\/g' \
| sed 's/\NULL\/\\N/g' \
| sed
Additionally, if a user has the SUPER privilege (eg. all privileges on
*.*) they can write to a database running in read-only mode. Yet
another reason to never allow this privilege for general purpose users.
Tyler
On 11/22/10 8:08 AM, John Daisley wrote:
The replicated database should not
Machiel,
Each table will be write locked while it is being altered so this will
most likely impact the application. In addition to the write lock, the
conversion causes each table to be completely rewritten in the new
format so this will have a high impact on IO write activity and so it
Tammie,
You might just try resetting the root password
http://dev.mysql.com/doc/refman/5.1/en/resetting-permissions.html#resetting-permissions-windows.
Hope this helps,
Tyler
On 10/19/10 12:38 PM, Montgomery, Tammie wrote:
I had an old version of mySQL on my computer but never used it. I
Charlene,
You should check the mysql error log and if there isn't a message about
the cause there you may want to check /var/log/syslog for mysql being
killed by oomkiller.
Tyler
On 6/21/10 11:11 AM, Charlene wrote:
Anybody have any idea why MySQL would start to have this error message
