Bug #70385 LCP Frag watchdog warning with weird numbers
Submitted: 20 Sep 2013 12:05 Modified: 20 Sep 2013 12:45
Reporter: Hartmut Holzgraefe Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:MySQL Cluster 7.2.7 OS:Linux
Assigned to: CPU Architecture:Any

[20 Sep 2013 12:05] Hartmut Holzgraefe 
Description:
Found this in a cluster log, happens roughly every 1-2 hours:

  2013-09-05 16:12:04 [MgmtSrvr] WARNING  -- Node 4: LCP Frag watchdog : No progress on table 4294967295, frag 4294967295 for 20 s.  184467440737095

The message seems to be truncate, the data node out.log has it as
  
  LCP Frag watchdog : No progress on table 4294967295, frag 4294967295 for 20 s.  18446744073709551615 rows completed

The values in this log message seem to be completely off the mark, the table and frag numbers are exactly 0xFFFFFFFF or 2^32-1 (all bits set), and 1.8*10^14 rows in a table or fragment doesn't sound realistic either 

How to repeat:
No idea, just found this in logs ..
[20 Sep 2013 12:45] MySQL Verification Team 
Duplicate of Bug 14680057, fixed in 7.0.37, 7.1.26, 7.2.10, and 5.7.1
[5 Apr 2019 6:25] Shawn Hogan 
Doesn't appear to be fixed.  Just ran across this same thing in logs with the latest version (mysql-5.7.25 ndb-7.6.9):

2019-04-04 22:57:06 [MgmtSrvr] WARNING  -- Node 16: LCP Frag watchdog : No progress on table 4294967295, frag 4294967295 for 21 s.  1168541 bytes r