percona-discussion team mailing list archive
-
percona-discussion team
-
Mailing list archive
-
Message #00593
Re: [Bug 378100] Re: Innodb locks up under large INSERT load
Can you give me steps to reproduce ? I will try on my box, thanks!
On Mon, May 18, 2009 at 2:53 PM, LCM <lmargulin@xxxxxxxxxx> wrote:
> Yes, it is release 5. It's innodb version 1.0.3-5a
>
> --
> 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.
>
--
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.
Follow ups
References