Re: How to setup cluster replication

[ewen fortune]

Hi,
Sounds like the ndb_schema tables havn't been created. These are
needed for ndb replication.
http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-replication-schema.html
"""
These tables are created during the MySQL installation process by the
mysql_install_db script,
and include a table for storing the binary log's indexing data.
"""

Ewen

On Mon, May 5, 2008 at 6:54 AM, Nick Cen <cenyongh@stripped> wrote:
> Hi All,
>
>  I wanna to build up a whole new cluster replication, i have 3 machines M1,
>  M2 and S2. M1 & M2 makeup the cluster. M2 and S2 makeup a replication
>  channel.
>  I am using the tar ball mysql-5.1.23-ndb-6.2.14-telco.tar. And follow the
>  instructions in this page
>  http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-replication-preparation.html
>  ,
>  the initial table is create with the mysql_install_db script.
>
>  The cluster is run without problem and here is the my.cnf in M2 and S2.
>
>  M2's my.cnf
>  [client]
>  default-character-set=utf8
>  [mysqld_safe]
>  default-character-set=utf8
>  # Options for mysqld process:
>  [mysqld]
>  ndbcluster                      # run NDB storage engine
>  ndb-connectstring=192.168.145.131  # location of management server
>  default-character-set=utf8
>  default-storage-engine=ndbcluster
>  # Replication
>  log-bin=mysql-bin
>  binlog-format=ROW
>  server-id=2
>  # Options for ndbd process:
>  [mysql_cluster]
>  ndb-connectstring=192.168.145.131  # location of management server
>
>  S2's my.cnf
>  [client]
>  default-character-set=utf8
>  [mysqld_safe]
>  default-character-set=utf8
>  # Options for mysqld process:
>  [mysqld]
>  ndbcluster
>  default-character-set=utf8
>  default-storage-engine=MyISAM
>  server-id=3
>
>  The bin-log file info is accquire with the following sql statement
>  mysql> flush tables with read lock;
>  Query OK, 0 rows affected (0.02 sec)
>  mysql> show master status;
>  +------------------+----------+--------------+------------------+
>  | File             | Position | Binlog_Do_DB | Binlog_Ignore_DB |
>  +------------------+----------+--------------+------------------+
>  | mysql-bin.000001 |      233 |              |                  |
>  +------------------+----------+--------------+------------------+
>  1 row in set (0.00 sec)
>
>
>  The cluster(M1,M2) and S2 can start without problem.
>
>  When i create a table in M2, a replicate table is create in S2. but when i
>  insert a record in to M2's table nothing happen in S2. And here is the
>  mysqld log of S2.
>  080505  7:38:01 [Note] Slave I/O thread: connected to master '
>  repl@stripped:3306',replication started in log 'mysql-bin.000001' at
>  position 233
>  080505  7:39:00 [ERROR] Slave SQL: Error 'Table 'mysql.ndb_apply_status'
>  doesn't exist' on opening table `mysql`.`ndb_apply_status`, Error_code: 1146
>  080505  7:39:00 [Warning] Slave: Table 'mysql.ndb_apply_status' doesn't
>  exist Error_code: 1146
>  080505  7:39:00 [Warning] Slave: Got error 4009 'Cluster Failure' from NDB
>  Error_code: 1296
>  080505  7:39:00 [ERROR] Error running query, slave SQL thread aborted. Fix
>  the problem, and restart the slave SQL thread with "SLAVE START". We stopped
>  at log 'mysql-bin.000001' position 322
>
>
>  Any idea, thanks in advance.
>
>  Nick
>