6 responses to “Creating a simple Cluster on a single LINUX host”

• 

  Gareth Bult June 20th, 2009 at 23:48

  Be interested to hear from other people running this sort of setup .. I run something almost identical (but with two management nodes) and have done for about 18 months. Reliability and performance are terrible and to date I’ve lost all my data twice. [in particular, it seems not to want to deal with power outages gracefully]

  Maybe it’s because I’m on a slightly older version, but given the problems I’ve had and the ones I’ve seen some people having upgrading, I’m pretty much afraid to touch it.

  I’ve also found the default action of using RAM rather than disk rather limiting, and although you can now use disk for some tables, it seems “fiddley”.

  Also (!) some things that work on other tables fail to work on NDB based tables .. although documented this isn’t necessarily all that obvious. For example I was caught out thinking I could just move current stuff to the cluster .. this fell down when I discovered full text indexing isn’t supported (!)

• 

  admin June 22nd, 2009 at 12:57

  Gareth,

  have you raised the data loss issue with the Cluster forum (http://forums.mysql.com/list.php?25) or the Cluster mailing list (cluster@lists.mysql.com)? While the advice would be to try to set things up such that a single power failure didn’t impact all of the data nodes making up a node group, that isn’t always possible and I wouldn’t expect data to be lost – if you haven’t done so already, raise the issue so that it can be identified whether there’s a bug or if there is something in your configuration that could be changed.

  You make a good point that it’s worth checking the known limitations of MySQL Cluster in the documentation before making the switch. Over time, the list will get shorter but there are things that MySQL currently can’t do that other storage engines can (e.g. foreign keys aren’t supported but you can simulate them using stored procedures).

• 

  Phil July 5th, 2009 at 18:00

  Hello Andrew,

  Great article – thanks a lot! I am really looking forward to the article you mentioned redarding the distribution amongst multiple servers.

  Cheers,
  Phil

• 

  Steve June 1st, 2010 at 00:49

  Hi.. How to know where i can find the configuration for localhost:1186 ? And what for we used this port ? Can you help me to show me, where i can found the configuration ? Because i try to connect to “ndb_mgm”, when i use “show” it shown “Unable to connect with connect string: nodeid=0, localhost:1186″. I try to look for that port with “netstat”, but i don’t find that port is listen.

• 

  Daniel Cabrera June 3rd, 2010 at 08:13

  Great work and thanks a lot for this guide.

  I´ve followed the instructions, and found some problems on ubuntu 10.04 and MySqlCluster 7.0.13 .

  I´d like to share this to people who migth find the same problems on ubuntu.

  First, the base_dir must be owned by mysql user( “mysql” in my system), else scripts/mysql_install_db fails to install the databases.
  It took me a while to discover this, but scripts/mysql_install_db runs flawlessly after running

  shell>chown -R mysql “extracted folder” ( in this guide /home/billy/mysql/7_0_6 )

  after creating the data folders

  Then, in the my.*.conf files, you must alter three lines :

  1.-> “log-bin” should read “log-bin=auth-bin” (or whatever log type you want ) to get rid of this warning when running mysqld

  ” No argument was provided to –log-bin, and –log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use ‘–log-bin=auth-bin’ to avoid this problem. ”

  2.-> You must add this line “user=mysql” to run bin/mysql without errors and security warnings

  3.-> Also,you should include “socket=/tmp/my.*.sock”
  were * is the nomber of the config file name(you could use whatever file name you want, they just have to be different for each config file) to connect to servers using bin/mysql.

  The command should be :

  shell>bin/mysql -h localhost -P 3306 \ –socket=/tmp/my.1.sock

  to avoid this error :

  ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)

  So, finally the conf/my.1.conf file should look like this :

  [mysqld]
  user=mysql
  ndb-nodeid=4
  ndbcluster
  datadir=”basedir”/data/data1
  basedir=”basedir”
  port=3306
  server-id=1
  log-bin=auth-bin
  socket=/tmp/my.1.sock

  Hope this helps to get this demo install running on Lucid Lynx

  Thanks again for your guide.

• 

  admin June 7th, 2010 at 10:37

  Hi Steve,

  1186 is the default port that the MySQL Cluster management node uses (can be override it in config.ini). When you run ndb_mgmd, it will listen to that port.

  Regards, Andrew.

6 Trackbacks / Pingbacks

• Deploying MySQL Cluster over multiple hosts @ Andrew Morgan’s MySQL Cluster Database Blog July 10th, 2009 at 19:33

  [...] post builds upon the earlier article (Creating a simple Cluster on a single LINUX host) which explained how to install and run a Cluster where all of the nodes run on the same physical [...]

• MySQL Cluster 7.0.7 source released @ Andrew Morgan’s MySQL Cluster Database Blog September 2nd, 2009 at 20:05

  [...] Following this you can configure and use the software as normal (refer to Creating a simple Cluster on a single LINUX host). [...]

• Accessing the same data through LDAP and SQL @ Andrew Morgan’s MySQL Cluster Database Blog October 9th, 2009 at 13:25

  [...] installed MySQL Cluster  – if that isn’t the case then please first refer to “Creating a simple Cluster on a single LINUX host” or “Deploying MySQL Cluster over multiple [...]

• Accessing the same data through LDAP and SQL « PlanetMysql.ru – информация о СУБД MySQL October 9th, 2009 at 16:10

  [...] installed MySQL Cluster  – if that isn’t the case then please first refer to “Creating a simple Cluster on a single LINUX host” or “Deploying MySQL Cluster over multiple [...]

• Using ClusterJ (part of MySQL Cluster Connector for Java) – a tutorial @ Andrew Morgan’s MySQL Cluster Database Blog March 30th, 2010 at 12:40

  [...] on ClusterJ rather than on running MySQL Cluster; if you are new to MySQL Cluster then refer to running a simple Cluster before trying this [...]

• Using ClusterJPA (part of MySQL Cluster Connector for Java) – a tutorial @ Andrew Morgan’s MySQL Cluster Database Blog March 31st, 2010 at 14:02

  [...] on ClusterJPA rather than on running MySQL Cluster; if you are new to MySQL Cluster then refer to Running a simple Cluster before trying these [...]