Bug #81763 | ndb_desc output should be deterministic independent of platform | ||
---|---|---|---|
Submitted: | 7 Jun 2016 21:31 | Modified: | 27 Jun 2016 11:40 |
Reporter: | Mauritz Sundell | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tests: Cluster | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[7 Jun 2016 21:31]
Mauritz Sundell
[14 Jun 2016 14:51]
Mauritz Sundell
Posted by developer: ndb_fully_replicated_restart fails also on Linux if it runs after ndb_index_stat_restart. Reason is that ndb_index_stat_restarts creates an extra hash map due to creating a table with one partition. Indexes created in ndb_fully_replicated_restart will get an id one higher than if the extra hashmap was not created, and the internal key in hash list of indexes will get another order. By listing index in id order the index order will be stable. Note, the extra hashmap is not visible from sql so mysqltest post test checks do not discover this change. And also there are currently no way to drop a hashmap.
[27 Jun 2016 11:40]
Jon Stephens
Documented fix in the NDB 7.5.3 changelog as follows: Table indexes were listed in the output of ndb_desc in a undefined order that could vary between platforms. Now these indexes are ordered by ID. Closed.