percona-discussion team mailing list archive

[Vadim Tkachenko <vadim@xxxxxxxxxxx>]

We use native InnoDB-plugin implementation, which was ported from Google 
rw_locks.

So all related features available - yes we have innodb_have_atomics 
variable.


> 
> It will be good to know whether this uses gcc atomics. Note that
> log_sys->mutex and the buffer pool mutex are mutex_t, not the innodb
> rw-mutex. The code for this is much simpler than for the rw-mutex.
> Alas, it doesn't have as much debugging information in it by default
> (such as the file name and line# for the last lock of it). That is
> enabled by UNIV_SYNC_DEBUG.
> 
> The v3 google patch displays whether gcc atomic are used by Innodb in
> either SHOW STATUS or SHOW VARIABLES. Does the Percona build have that
> feature?


-- 
Vadim Tkachenko, CTO
Percona Inc.
ICQ: 369-510-335, Skype: vadimtk153, Phone +1-888-401-3403
MySQL Performance Blog - http://www.mysqlperformanceblog.com
MySQL Consulting http://www.percona.com/

-- 
Innodb locks up under large INSERT load
https://bugs.launchpad.net/bugs/378100
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona-XtraDB.

Status in Percona XtraDB Storage Engine for MySQL: New

Bug description:
While trying to load a new db on the 5.1.34-xtradb build, the Innodb engine locks up after a few minutes with multiple table loads running.

I can still log into the server, but I don't get any data back from the SHOW ENGINE INNODB STATUS command. I also can't kill any of the existing INSERT commands. I can reproduce the problem with as few as 3 simulateous loads (INSERT) occurring.

I am running this on SuSE version 10 with 8 processors and 126GB of RAM. 

Can I get some help in troubleshooting this? There are no messages being written to the error log.