Description:
In debugging another issue, I ran into this one. The test below will hang mysql-test and
not return. Looking at TOP you see that the ndbd's are getting CPU time, but still the
test never returns.

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1709 root      16   0  2740  612  528 S  0.3  0.0   7:29.38 nifd
14599 ndbdev    15   0  322m 161m 2876 S  0.3  5.3   0:02.01 ndbd
14615 ndbdev    15   0  322m 161m 2744 S  0.3  5.3   0:02.02 ndbd

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1709 root      16   0  2740  612  528 S  0.3  0.0   7:29.44 nifd
14599 ndbdev    15   0  322m 161m 2876 S  0.3  5.3   0:02.13 ndbd
14615 ndbdev    15   0  322m 161m 2744 S  0.3  5.3   0:02.15 ndbd

How to repeat:
--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
create table t1 (word char(20) not null PRIMARY KEY)ENGINE=NDB;
load data infile '../../std_data/words.dat' into table t1 ;
select count(*) from t1;
DROP TABLE t1;

Thank you for a problem report. Can you, please, try to repeat it on 5.1.7-beta and inform
about the results?

verified in 5.1.7 

./mysql-test-run --start-and-exit --do-test=ndb

create table t1 (word char(20) not null PRIMARY KEY)ENGINE=NDB;
load data infile '../../std_data/words.dat' into table t1 ;

... hangs

see 17081

pushed into 5.0.19

will be pushed into 5.1.7 one merge jam is released

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2225

pushed to 5.1.7

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented fix in 5.1.7 changelog. Bug closed.