Query Stalls and High Memory Usage When Querying Table That Exists In the Data Nodes But Not the SQL Node; Data Nodes On Same Host May Encounter Watchdog Warnings
Last updated on MARCH 08, 2017
Applies to:MySQL Cluster - Version 7.0 and later
Information in this document applies to any platform.
Using one of the following versions:
- MySQL Cluster 7.0 before 7.0.41
- MySQL Cluster 7.1 before 7.1.30
- MySQL Cluster 7.2 before 7.2.15
- MySQL Cluster 7.3 before 7.3.10
- MySQL Cluster 7.4 before 7.4.7
and querying a table that does not exists in the SQL node but the table does exist in the data nodes,
After that includes one or more tables in databases that do not exist in the mysqld node (though see also the first special case below), the following occurs when querying one of the tables that exists in the data node but not the SQL node:
- The query seems to hang, but will eventually fail. The exact failure will vary; a typical failure is:
If there are any data nodes on the same host, the high load may cause watchdog warnings potentially to the extend that the data node is shut down.
The schema has been restored from a backup using ndb_restore ... --restore_meta.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms