imulating your workload, but I only get 25 segments. No leak
seen.
Regards,
Heikki
- Original Message - From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 8:17 PM
Subject: Re: InnoDB data files keep growi
Heikki,
Heikki Tuuri wrote:
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routine first prints inode pages
that are completely used, and after that other inode pages. Since the
tablespace validation said the tablespace is ok, I guess
Heikki,
Heikki Tuuri wrote:
InnoDB is clearly leaking 'segments' in the system tablespace. They are
probably undo logs. For some reason, a trx commit or purge fails to free
them.
SEGMENT id 0 75994 space 0; page 82136; res 2720 used 2680; full ext 41
fragm pages 32; free extents 0; not full exte
Heikki,
I can think of another explanation. Are you sure that all your tables
really are in .ibd files? Maybe some older tables are actually in the
ibdata files?
Yes I'm sure they're all in .ibd files (and I've just checked just in case
- they are indeed).
Please use the innodb_tablespace_monito
Heikki,
the output shows that there are no dangling transactions, and purge is
not lagging behind.
Yes, that's what I thought... weird, huh :/
If you update a secondary index column, that requires purge to clean up
the index.
The tables have structure similar to the following:
create table table1
d 593305, updated 1606540, deleted 0, read 453171610
1.79 inserts/s, 4.00 updates/s, 0.00 deletes/s, 571.89 reads/s
--------
END OF INNODB MONITOR OUTPUT
- Original Message - From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: maili
Hello,
I have a DB of about 100 tables, and MySQL is configured to keep them in separate files. Total size
of the files is ~2GB. Most of the tables are of similar format and consist of many short
fixed-length rows (~50 bytes/row). The database size is increased for several MB a day.
Initial conf
