Alejandro Gad wrote:
> Hi!
>
> I could see that by default this variable is enabled, but how this variable can
> affect the cluster if it is False?
> is recommend to leave as default ?
>
> I am asking because of this errors and i have "StopOnError = false" in config.ini
>
> Cluster 192.168.222.37: Lock wait timeout exceeded; try restarting transaction
> |
> Cluster 192.168.222.36: Got temporary error 4010 -Node failure caused abort of
> transaction- from ndbcluster |
> Cluster 192.168.222.36: Got temporary error 1204 -Temporaryfailure, distribution
> changed- from ndbcluster |
> Cluster 192.168.222.36: Got temporary error 4025 -Node failure caused abort of
> transaction- from ndbcluster |
> Cluster 192.168.222.37: Lock wait timeout exceeded; try restarting transaction
> |
> Cluster 192.168.222.36: Got temporary error 4031 -Node failure caused abort of
> transaction- from ndbcluster |
> Cluster 192.168.222.37: Got temporary error 270 -Transaction aborted due to node
> shutdown- from ndbcluster |
> Cluster 192.168.222.37: Lock wait timeout exceeded; try restarting transaction
> |
> Cluster 192.168.222.37: Lock wait timeout exceeded; try restarting transaction
> |
> Cluster 192.168.222.36: Got temporary error 4010 -Node failure caused abort of
> transaction- from ndbcluster |
>
> To solve this errors i have to do a ndbd --initial and restore a mysqldump backup.
>
> Thanks!
> #from mysql manual
>
> [NDBD]StopOnError
> This parameter specifies whether an NDBD process is to exit or to perform an
> automatic restart when an error condition is encountered.
> This feature is enabled by default.
>
> Alejandro
>
Hi, Alejandro
You have found a bug somewhere. The ndbd node shold not crash,
regardless of StopOnError setting.
The StopOnError=false only makes the ndbd process restart after
detecting the bug.
If you could make a reproducable test case of this and report it at
http://bugs.mysql.com that would be very good.
/Jonas
--
Jonas Oreland, Software Engineer
MySQL AB, www.mysql.com
