MySQL Bugs: #12942: MySQL Cluster doesn't response more than 4 minutes

Bug #12942	MySQL Cluster doesn't response more than 4 minutes
Submitted:	2 Sep 2005 2:55	Modified:	24 Sep 2005 13:58
Reporter:	Kenji Hirohama	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	4.1.13	OS:	Miracle Linux 3.0：Linux 2.4.21-9
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
If I do the following at the same moment, I cannot get any reply more than 4 minutes.

1. Issuing a update stament
2. Making the interconnect between a SQL Node and a Data Node down

After 4 minutes, the transaction is handled properly.

How to repeat:
Configure MySQL Cluster to use two different networks for;
1. SQL Node and Data Node commumication
2. Data Node and Data Node communication

Then, issue any update states like;
update t1 set c2=1 where c1=1;

At the "same" moment;
ifconfig eth0 down;

The update statement doesn't reply any response more than 4 minutes always.
After 4 minutes, quesry reply "OK"

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:

Currently unsupported configuration. Updated Limitations section of NDB Cluster chapter in Manual per info from DavidA.