MySQL Forums
Forum List  »  NDB clusters

Re: mysql -h --user=root -p < /u00/mydbcl/backup.sq and recieved this error: ERROR 1036 (HY000) at line 418: Table 'ndb_apply_status' is read only
Posted by: Mikael Ronström
Date: October 18, 2017 06:11PM

I presume you mean that you used MySQL Cluster 7.5 that is based on
MySQL 5.7.

First off replication is setup also when you setup using the auto
installer. The thing is that the NDB storage engine handles replication
internally using synchronous replication.

Interestingly you can also use MySQL replication between clusters where
we have synchronous replication using the NDB storage engine internally
in each cluster and various advanced schemes for setting up replication
between those clusters.

Here is a cut that describes the use of the ndb_apply_status table:

The ndb_apply_status table contains rows that describe epochs that are written into the cluster by a slave applier. So updates to this table is not generated by events in the cluster, it is generated by a MySQL replication server. Thus in the master cluster this table would be empty, the table will be filled in the slave cluster when applying the epoch in the slave. This table has a primary key that is the server id, thus each epoch will overwrite the values in this tables. Only the latest applied epoch is represented in this table for each server id.

Why the ndb_apply_status table is read only I do not know.

The ndb_apply_status table is an NDB table.

I'll ask someone tomorrow with more in-depth understanding of these parts
and see if they know reasons why that could happen.

Edited 1 time(s). Last edit at 10/18/2017 06:13PM by Mikael Ronström.

Options: ReplyQuote

Written By
Re: mysql -h --user=root -p < /u00/mydbcl/backup.sq and recieved this error: ERROR 1036 (HY000) at line 418: Table 'ndb_apply_status' is read only
October 18, 2017 06:11PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.