tablecrash on MySQL-Max-4.0.16

Vidar <[email protected]>
Newsgroups gmane.comp.db.mysql.bugs
Message-ID <[email protected]>
Hi

system : rh9
mysql :
MySQL-devel-4.0.16-0
MySQL-shared-4.0.16-0
MySQL-Max-4.0.16-0
MySQL-client-4.0.16-0
MySQL-server-4.0.16-0

We have a table 
> desc ezsession;
+-----------------+------------------+------+-----+---------+-------+
| Field           | Type             | Null | Key | Default | Extra |
+-----------------+------------------+------+-----+---------+-------+
| session_key     | varchar(32)      |      | PRI |         |       |
| expiration_time | int(11) unsigned |      | MUL | 0       |       |
| data            | text             |      |     |         |       |
| cache_mask_1    | int(11)          |      |     | 0       |       |
+-----------------+------------------+------+-----+---------+-------+

This table is very often read/written to (only plain select, insert and update 
queries, no joins). But sometimes it crashes. I have uploaded 
tablecrash_max4016_full_processlist.tar.gz to your ftp account

The table locks, so a restart of mysql and a "repair table ezsession;" is 
needed in order to make the table work again.
The table have typically 10000-20000 records
> select avg(length(data)) from ezsession;
+-------------------+
| avg(length(data)) |
+-------------------+
|          667.3505 |
+-------------------+
1 row in set (0.09 sec)

mysql> select max(length(data)) from ezsession;
+-------------------+
| max(length(data)) |
+-------------------+
|              4214 |
+-------------------+
1 row in set (0.08 sec)


I realize this is not much for you to go on, put any hint which could help me 
create a repeatable testcase is appreciated. Maybe you allready are aware of 
similar problems?

Also, it seems that the size of "data" might be related. Some codechange in 
our application to reduce the size in this field seemed to help, (less 
frequently crashes)

The server is not installed with your precompiled binaries either so this 
might be a place to start ?

PS
This is definitively  NOT a "disk full" problem

-- 
Vidar Langseid



-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.