Il 17/02/2011 22:28, Natxo Asenjo ha scritto:
hi,
our mysql database has a growing ibdata1 file that is starting to fill
the /var partition. STFW recommends dumping the opsview database and
recreating it.
I have read the opsview recommendations
http://docs.opsview.org/doku.php?id=opsview3.0:prereqs#mysql and used
the options.
innodb_file_per_table=1
innodb_flush_log_at_trx_commit=2
These option affect only tables and databases created after they are
set. So tables created before setting them, are in ibdata1 file.
I have applied them (debian lenny mysql server) and restarted the
mysql daemon. Should I now backup the opsview database, drop it, and
recreate it while the opsview daemons are stopped?
Dropping database in pre 5.5 mysql version (or 5.1 using innodb plugin
1.0.x, not enabled by default) don't shrink shared tablespace (ibdata1)
after tables are removed. So the tablespace il large, but space is
marked as unused.
I advice you to do a full backup, stop mysql server, move ibdata file to
another directory (or remove it if you are confident with data backups
and their integrity), restart mysql, restore backup.
DON'T DO THIS ON PRODUCTION SYSTEMS before you are 100% confident with
these techniques, as you can loose all your data. Practice with non
critical installations where data is not important.
How can I prevent this file from growning again?
Doing all the steps correctly ensure that ibdata1 is not used by most of
the tables (mysql still needs it, but it should be rather small).
Perhaps each table will have a tablespace that grows as data is inserted
by opsview.
You must configure correctly data retention on opsview to avoid to fill
up the storage.
--
Groeten,h
natxo
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
