MySQL Bugs: #18746: Restarting non-master data node can produce error '1204 ..distribution changed'

Bug #18746	Restarting non-master data node can produce error '1204 ..distribution changed'
Submitted:	3 Apr 2006 15:29	Modified:	8 Apr 2006 5:28
Reporter:	Serge Kozlov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	5.1.9 (beta)	OS:	Linux (FC4)
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
DBD::mysql::st execute failed: Got temporary error 1204 'Temporary failure, dist
ribution changed' from NDBCLUSTER at ./load_tpcb.pl line 400.
insert into account Error: Got temporary error 1204 'Temporary failure, distribu
tion changed' from NDBCLUSTER at ./load_tpcb.pl line 400.

How to repeat:
1. Create new cluster config with 1 mgmd, 3
ndbd/3 Replicas, 1 mysqld, 1 api. All nodes placed on one machine.
2. Start cluster
3. Run ./load_tpcb.pl ndb16 3306 root BLANK ndb.
4. Wait while  the script will show 'Loading accounts table -- Please wait'.
5. Resart any non-master node (X RESTART).
Sometimes  the script stopped with error described above in 'Description' section.

Hi,

This is expected behavior
1) Stop of any node (master/non master) one could get a bunch of different
    errors. All of the should have the ndb classification node failure.
    The only expection to this is that when doing a graceful shutdown...there shouldnt
    be any aborted transactions.

2) During start of a node. One can get 1204 (and probably some other too...)
    These are also temporary errors.

All of these errors must be handled within application.
Basic rule for our internal test programs are: retries the transaction on any temporary error.

Please mail if you got any questions.

Hi,

Jon, this behaviour is not documented...(among other things...)

Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

Updated 4.1/5.0/5.1 Cluster Limitations transaction handling section with info provided. Closed.