Skip to main content
Database Administrators

Return to Answer

Commonmark migration
Source Link
Community Bot
Community Bot
  • 1

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

GIVE IT A TRY !!!

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

GIVE IT A TRY !!!

replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's TablespaceFill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

fixed variable MYSQL_USER in the MYSQL_CONN string
Source Link
edit approved Dec 1, 2016 at 15:19
Michel Feldheim
edit approved Dec 1, 2016 at 15:19
Michel Feldheim
  • 57
  • 11

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_CONNMYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_CONN} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

You could have InnoDB clean things up as follows:

  • signal mysqld to have InnoDB flush everything out of the logs on shutdown
  • shutdown mysqld
  • delete the logs
  • start mysqld

No crash recovery will happen because there will be nothing to recover.

MYSQL_USER=root
MYSQL_PASS=rootpassword
MYSQL_CONN="-u${MYSQL_USER} -p${MYSQL_PASS} -h127.0.0.1 -P3306 --protocol=tcp"
SQL="SET GLOBAL innodb_fast_shutdown = 0"
mysql ${MYSQL_CONN} -ANe"${SQL}"
mysqladmin ${MYSQL_CONN} shutdown
cd /var/lib/mysql
rm -f ib_logfile*
service mysql start

If you want lingering data pages cleansed out of the Double Write Buffer, please see my old post Fill ibdata1 With Zeros/Nulls/etc Or Change A Table's Tablespace

#GIVE IT A TRY !!!

Source Link
RolandoMySQLDBA
RolandoMySQLDBA
  • 184.3k
  • 33
  • 323
  • 531