Mayuran Yogarajah [EMAIL PROTECTED] wrote:
Is there some way to trim the 50gb+ file down ?
Yes, dump the databases using mysqldump, then recreate the autoextend
InnoDB tablespace and then run the .sql script.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
Currently we have one way master to slave replication setup.
The master has 2 innodb data files, the second has now grown
to 50gb+. The slave's innodb data files are less than 2 gigs.
How is this possible? They are both storing the exact same
data. Is there some way to trim the 50gb+ file down ?
Mayuran,
Well, I´m not a MySQL expert, but I think that a good
configuration in the my.cf file can make it better.
Ronan
- Original Message -
From: Mayuran Yogarajah [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 26, 2004 5:37 PM
Subject: huge innodb data files
Our DB
]
Subject: Re: huge innodb data files
Date: Fri, 27 Aug 2004 09:49:51 -0300
Mayuran,
Well, I´m not a MySQL expert, but I think that a good
configuration in the my.cf file can make it better.
Ronan
- Original Message -
From: Mayuran Yogarajah [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent
26, 2004 5:37 PM
Subject: huge innodb data files
Our DB in production currently has 2 innodb data files,
the second one (which is marked autoextend) has now
grown past 26 gigs. We are experiencing weird speed
problems with one of the tables. Even though there are
no rows in this table, performing
Our DB in production currently has 2 innodb data files,
the second one (which is marked autoextend) has now
grown past 26 gigs. We are experiencing weird speed
problems with one of the tables. Even though there are
no rows in this table, performing any kind of select takes
about 2 minutes to
