Bug #102729 ndb_import can easily hang at errors and at high load
Submitted: 25 Feb 3:41 Modified: 26 Feb 15:27
Reporter: Mikael Ronström Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:8.0.23 OS:Any
Assigned to: CPU Architecture:Any

[25 Feb 3:41] Mikael Ronström
Description:
ndb_import can hang after errors, but also without any specific
reason it simply stops. This is usually the case when running at
high load.

How to repeat:
Run ndb_import to load large data sets, e.g. DBT2 CSV files (requiring
some fixes to handle AUTO_INCREMENT in the history table).

Suggested fix:
Unknown for the moment
[25 Feb 8:03] MySQL Verification Team
Hello Mikael,

Thank you for the report and feedback.

Sincerely,
Umesh
[26 Feb 15:27] Mikael Ronström
A bit more analysis shows that it gets an error e.g. 630, tuple
already exist or Out of Data Memory. But instead of stopping on
the first error as the default settings are and reporting the
error, it simply hangs instead. Hangs is maybe the wrong word
since the process is continously checking for things, but all
progress stops.