Bug #21875 | "create table" fails in NDB with error 156 | ||
---|---|---|---|
Submitted: | 28 Aug 2006 14:09 | Modified: | 28 Sep 2006 5:09 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 5.0.23 and up | OS: | Linux (Linux (ia64)) |
Assigned to: | Martin Skold | CPU Architecture: | Any |
[28 Aug 2006 14:09]
Joerg Bruehe
[28 Aug 2006 14:13]
Jonas Oreland
unless you have changed icc version this is 99% a duplicate of http://bugs.mysql.com/bug.php?id=17621
[28 Aug 2006 14:29]
Joerg Bruehe
Sorry, my search had not led me to that entry. The compiler was upgraded: [mysqldev@rx2620b mysqldev]$ . path-for-rx2620b [mysqldev@rx2620b mysqldev]$ icc -V Intel(R) C Itanium(R) Compiler for Itanium(R)-based applications Version 9.1 Build 20060523 Package ID: l_cc_c_9.1.039 Copyright (C) 1985-2006 Intel Corporation. All rights reserved. This is the "configure" line (from "max"): CC=icc CFLAGS="-O3 -unroll2 -ip -mp -restrict" CXX=icpc CXXFLAGS="-O3 -unroll2 -ip -mp -restrict" LDFLAGS="-static-libcxa -i-static" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --with-comment="MySQL Community Edition - Experimental (GPL)" --with-server-suffix="-max" --enable-thread-safe-client --enable-local-infile --with-pic --with-fast-mutexes --disable-shared --with-zlib-dir=bundled --with-big-tables --with-readline --with-archive-storage-engine --with-blackhole-storage-engine --with-ndbcluster --with-csv-storage-engine --with-example-storage-engine --with-federated-storage-engine --with-innodb --with-extra-charsets=all If dropping "-ip" had helped you, we can of course do a run with the new compiler without that option.
[29 Aug 2006 13:03]
Jonas Oreland
Is it correct that it only fails with icc ? Then skip icc build for ndb Assigning to martin so he can agree/disagree.
[20 Sep 2006 9:51]
Mads Martin Joergensen
Upgrade of icc "fixed" this, so this is not a bug in our code, but was a bug in the icc we were using. Setting to documenting, just in case we want to document this in some way.
[25 Sep 2006 8:10]
Jon Stephens
I think that this should be documented in the 5.0/5.1 Manual under Installation/Building From Source, but first a stupid question - what were the "old" and "new" icc versions? (I've never used icc myself and am not sure where to get this info.) Also, were any 4.1 versions of the server affected by this problem? Thanks!
[25 Sep 2006 8:39]
Joerg Bruehe
About 4.1: I cannot tell for sure. We did not notice this specific problem in 4.1.20 or 4.1.21, but I cannot tell the reason (code differences so that this compiler bug was not triggered, or test differences so that it was not shown, or ...) About "icc" versions: The "new" vesion is called 9.1.043, and the compiler shows this output: mysqldev@nocona:~> icc --version icc (ICC) 9.1 20060818 Copyright (C) 1985-2006 Intel Corporation. All rights reserved. The previous version, which had the problem, was 9.1.039, identifying as icc (ICC) 9.1 20060523 Note that all this is specific to "ia64" CPUs, the problem never occurred on "x86" or "x86_64".
[28 Sep 2006 5:09]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Added a note about this issue to the Porting section in the 5.0 and 5.1 Manual. Thanks for the info.