FYI I often get this same error when trying to load data. I'll restart the
transaction, I'll drop the table and reload. Same result. And nothing in any
error log. Seems like adjusting parameters in config.ini should fix, but so far
I've found no magic bullet.
> We're giving Cluster a go on a lab database cluster with some sample
> datasets before allocating any real hardware to it. We have a dump from
> another mysql server that is about 250 MB in size, and trying to
> import it
> into our mysqld node in the cluster results in the following error
> more than an hour of importing (using mysql < import.file):
> ERROR 1205 (HY000) at line 559: Lock wait timeout exceeded; try
In some cases this error code could occur due to a node failure. Check
if any strange things occurred.
> Our cluster config is 3 hosts: 2x servers with 1024MB RAM and
> 2-PIII/850MHz and SCSI disks, one box 128MB RAM and 1-PIII/700MHz and
> disk. The two servers with 1GB RAM are the NDB nodes, the other is the
> and MGM node. Below is our config.ini for the cluster. Could this
> error be
> the result of low system resources on the SQL node, or are there
> that we should adjust in the config? And what would cause the import to
> take over an hour for a 250 MB database?
> [NDBD DEFAULT]
> [TCP DEFAULT]
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!