percona-discussion team mailing list archive

[MARK CALLAGHAN <mdcallag@xxxxxxxxx>]

On Mon, May 18, 2009 at 4:23 PM, LCM <lmargulin@xxxxxxxxxx> wrote:
> I didn't do much. I exported my existing 4.1 db. Each table is exported
> to a separate file that is gzipped. On my new 5.1 instance with the
> XtraDB build, I am running multiple sessions. Each session is just
> importing a different subset of tables.
>
> In experimenting with this, it seems as though there may be something
> happening with the innodb log file. I initial had 3 log files, each
> 1,000MB with a INNODB_MAX_DIRTY_PAGES_PCT of 15. Running 6 table
> imports, the db would lock up after about 3 minutes. I went to 128MB X 3
> log files and DIRTY_PAGES=90 and the db would lock in a few seconds,
> again with 6 imports running. I have been able to recreate the lock up
> with as few as 3 imports, but it does take longer to run into the
> problem.
>
> I built the initial innodb data file at 600GB. I have about 550 tables
> to import. All of these tables with indexes use up about 550GB of disk
> space. I initial built this server with MySQL 5.0 and didn't experience
> any of these problems.
>
> Let me know if there is any additional info I can provide that would be
> helpful. I was hoping to use the XtraDB engine to find some
> performance/stability over the 5.1 from MySQL. Since we are having other
> crash issues with the standard MySQL 5.1 release
>
> Lee

Can you get thread stacks when it gets stuck?

See this for the gdb command line to get thread stacks from a running server:
http://dammit.lt/2009/02/15/poor-mans-contention-profiling/

-- 
Mark Callaghan
mdcallag@xxxxxxxxx