Bug #76325 NDB ANALYZE TABLE HANG WHEN INDEX STAT UPDATE FAILS ON ONLY ONE INDEX
Submitted: 15 Mar 2015 12:39 Modified: 15 May 2015 16:03
Reporter: Pekka Nousiainen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:7.1 OS:Any
Assigned to: CPU Architecture:Any

[15 Mar 2015 12:39] Pekka Nousiainen
Description:
Table with multiple indexes.
Create (via code) random errors on index stats update.
A second analyze table afterwards can hang.

How to repeat:
Above.

Suggested fix:
Fix stats update error processing in handler.
[15 May 2015 16:03] Jon Stephens
Documented fix in the NDB 7.3.10, 7.4.7, and 7.5.0 changelogs, as follows:

    NDB statistics queries could be delayed by the error delay set
    for ndb_index_stat_option (default 60 seconds) when the index
    that was queried had been marked with internal error. The same
    underlying issue could also cause ANALYZE TABLE to hang when
    executed against an NDB table having multiple indexes where an
    internal error occured on one or more but not all indexes.

    Now in such cases, any existing statistics are returned
    immediately, without waiting for additonal statistics to be
    discovered.

Closed.