Alagar samy wrote:
> Hello,
>
> i have few queries regarding source of mysql-5.1.39 and
> mysql-cluster-gpl-5.1.39_7.0.9 .
>
> $ grep -i -r column_bitmaps_signal mysql-5.1.39/sql/handler.cc
> void handler::column_bitmaps_signal()
>
> $ grep -i -r column_bitmaps_signal mysql-cluster-gpl-7.0.9/sql/handler.cc
> void handler::column_bitmaps_signal(uint sig_type)
>
> there are quite a lot difference in innodb source provided by mysql-5.1.39
> and mysql-cluster-gpl-5.1.39_7.0.9b .. and the above mentioned diff is
> significant as it causes problem during server startup if we have
> ha_innodb.so from mysql-5.1.39 and mysqld binary from
> mysql-cluster-gpl-5.1.39_7.0.9b .. (as of now, we have desiged as this
> is going to be our deployment model).
Hi Algar,
I'm sorry, but his type of deployment is simply not supported. If you
use binaries built by MySQL, they must have the same version string. If
you build from source, you must use the same source for building all
MySQL Cluster binaries. The only exception to this is when performing
online upgrades between MySQL Cluster versions.
In addition, we stopped supporting the NDB storage engine in mainline
MySQL 5.1 quite some time ago -- as of MySQL 5.1.24. In fact, the second
paragraph on http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster.html
states,
"Beginning with MySQL 5.1.24, support for the NDBCLUSTER storage engine
was removed from the standard MySQL server binaries built by MySQL.
Instead, users of MySQL Cluster binaries built by MySQL should upgrade
to the most recent binary release of MySQL Cluster NDB 6.3 or MySQL
Cluster 7.0 for supported platforms — these include RPMs that should
work with most Linux distributions. MySQL Cluster users who build from
source should be aware that, also beginning with MySQL 5.1.24,
NDBCLUSTER sources in the standard MySQL 5.1 tree are no longer
maintained; these users should use the sources provided for MySQL
Cluster NDB 6.2 or later."
The first item in the 5.1.24 changelog
(http://dev.mysql.com/doc/refman/5.1/en/news-5-1-24.html) contains a
similarly-worded statement.
The bottom line is that you must use mysqld's that are compiled with NDB
support if you want them to connect to a MySQL Cluster, MySQL 5.1 mysqld
binaries built by MySQL don't include NDB, and you cannot hope to
compile mysqld with NDB support using the 5.1 sources.
I suggest you re-think your requirements. :)
cheers
jon.
>
>
> this is the error that we are getting,
> 091114 0:54:53 [ERROR] Can't open shared library
> '/usr/lib64/mysql/plugin/ha_innodb.so' (errno: 34 undefined
> symbol: _ZN7handler21column_bitmaps_signalEv)
> 091114 0:54:53 [ERROR] Couldn't load plugin named 'innodb' with soname
> 'ha_innodb.so'.
>
> are sources/binaries from mysql-5.1.39 and mysql-cluster-gpl-5.1.39_7.0.9b
> incompatible? (though cluster-7.0.9b is just applied to mysql-5.1.39 to
> create mysql-cluster-gpl-5.1.39_7.0.9) .. if so, what about sources for
> other tools/scripts/binaries between mysql-5.1.39 and
> mysql-cluster-gpl-5.1.39_7.0.9b ... are there incompatibilities in that
> as well ?
>
> thanks,
> A.Alagarsamy
>
>
> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
> http://in.yahoo.com/
>
> --
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe: http://lists.mysql.com/cluster?unsub=1
>
>
--
Jon Stephens - jon.stephens@stripped
Technical Writer
MySQL Documentation Team
Sun Microsystems AB
MySQL and Software Infrastructure Group
Liljeholmen (Stockholm), Sweden
Summer: UTC +02.00 / Winter: UTC +01.00
Mobile: +46 (0) 736 773 993
Skype: plastic-fish
MySQL: www.mysql.com
Sun: www.sun.com
