Re: Error 1112 on Innodb to ndb replication

[Vasilis Kioustelidis]

Hi Frazer,
from what you are saying it seems that it is not possible to setup slave replication to an NDB cluster. Is this the case or there actually some way to set this up in the management node or data node instead?


This is a dump of the tables you mentioned and I only have one replication setup.


USE performance_schema;
SELECT * FROM replication_connection_configuration\G
*************************** 1. row ***************************
CHANNEL_NAME: my_channel_1
HOST: ***.***.***.***
PORT: 3306
USER: repl
NETWORK_INTERFACE:
AUTO_POSITION: 0
SSL_ALLOWED: NO
SSL_CA_FILE:
SSL_CA_PATH:
SSL_CERTIFICATE:
SSL_CIPHER:
SSL_KEY:
SSL_VERIFY_SERVER_CERTIFICATE: NO
SSL_CRL_FILE:
SSL_CRL_PATH:
CONNECTION_RETRY_INTERVAL: 60
CONNECTION_RETRY_COUNT: 86400
HEARTBEAT_INTERVAL: 30.000
TLS_VERSION:
PUBLIC_KEY_PATH:
GET_PUBLIC_KEY: NO
NETWORK_NAMESPACE:



SELECT * FROM replication_connection_status\G
*************************** 1. row ***************************
CHANNEL_NAME: my_channel_1
GROUP_NAME:
SOURCE_UUID: a7978fd4-7b17-11e9-bcef-984be16f86dc
THREAD_ID: 123
SERVICE_STATE: ON
COUNT_RECEIVED_HEARTBEATS: 0
LAST_HEARTBEAT_TIMESTAMP: 0000-00-00 00:00:00.000000
RECEIVED_TRANSACTION_SET:
LAST_ERROR_NUMBER: 0
LAST_ERROR_MESSAGE:
LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION: ANONYMOUS
LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 2019-08-30 22:05:34.223820
LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 2019-08-30 22:05:34.223846
QUEUEING_TRANSACTION:
QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 0000-00-00 00:00:00.000000

SELECT * FROM replication_applier_configuration\G
*************************** 1. row ***************************
CHANNEL_NAME: my_channel_1
DESIRED_DELAY: 0


SELECT * FROM replication_applier_status\G
*************************** 1. row ***************************
CHANNEL_NAME: my_channel_1
SERVICE_STATE: OFF
REMAINING_DELAY: NULL
COUNT_TRANSACTIONS_RETRIES: 0

SELECT * FROM replication_applier_status_by_worker\G

*************************** 1. row ***************************
CHANNEL_NAME: my_channel_1
WORKER_ID: 0
THREAD_ID: NULL
SERVICE_STATE: OFF
LAST_ERROR_NUMBER: 1112
LAST_ERROR_MESSAGE: Error 'Table 'network_stats' uses an extension that doesn't exist in this MySQL version' on query. Default database: 'my_db'. Query: '*****'
LAST_ERROR_TIMESTAMP: 2019-08-28 14:17:23.115998
LAST_APPLIED_TRANSACTION:
LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000
LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000
APPLYING_TRANSACTION: ANONYMOUS
APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000
APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2019-08-28 14:17:23.103355
LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0
LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0
LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE:
LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
APPLYING_TRANSACTION_RETRIES_COUNT: 0
APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0
APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE:
APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000


SELECT * FROM replication_applier_status_by_coordinator\G
Empty set (0.00 sec)


SELECT * FROM replication_group_member_stats\G
Empty set (0.00 sec)

SELECT * FROM replication_group_members\G
Empty set (0.00 sec)