After ALTER TABLE Adding a Dynamic Column Follwed By a Cluster Restart, Some Primary Key Lookups Do Not Return a Row (Doc ID 1637292.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Cluster - Version 7.2 and later
Information in this document applies to any platform.

Symptoms

When selecting a row by PRIMARY KEY, the row is not returned even if the row exists.

Changes

The cluster has gone through the following history:

  1. A table was created in a version using default hash map size 240 (MySQL Cluster 7.1 and earlier and MySQL 7.2.6 and earlier). The number of partitions for the table cannot factor 240.
  2. The cluster was upgraded to a version using default hash map size 3840 (MySQL 7.2.7 and later and MySQL 7.3 and later).

Alternatively the option DefaultHashMapSize has been changed from 240 to 3840.

After the change to the hash map size, the following steps have been performed:

  1. Add a column that is added as a dynamic field, for example:
     
  2. Do a system restart.

Cause

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