MySQL Forums
Forum List  »  NDB clusters

Re: Error 1112 on Innodb to ndb replication
Posted by: Vasilis Kioustelidis
Date: August 26, 2019 10:16AM

Hi Frazer,
I have a single replication channel between the two setups so it should work.
I looked into the mysqld erro file (/var/log/mysqld.log) and I discovered several errors related to out-of-memory issues:

2019-08-26T16:07:02.831546Z 0 [ERROR] [MY-010934] [Server] Out of memory (Needed 1047216154 bytes)
2019-08-26T16:07:02.831556Z 0 [ERROR] [MY-010934] [Server] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
2019-08-26T16:07:02.831570Z 0 [Note] [MY-010866] [Server] NDB Metadata: Failed to fetch schema names from DD
2019-08-26T16:07:02.831584Z 0 [Note] [MY-010866] [Server] NDB Metadata: Failed to detect table metadata changes
2019-08-26T16:07:02.831592Z 0 [Note] [MY-010866] [Server] NDB Metadata: Table metadata check completed
2019-08-26T16:07:02.831599Z 0 [Note] [MY-010866] [Server] NDB Metadata: Metadata check completed
2019-08-26T16:08:02.831702Z 0 [Note] [MY-010866] [Server] NDB Metadata: Metadata check started

Running top as suggested gives me:
12833 mysql 20 0 3424684 666500 6248 S 1.3 35.4 1309:58 mysqld
14296 mysql 20 0 1155388 2044 1752 S 0.7 0.1 768:15.12 mysqld-debug
1 root 20 0 136356 4184 2496 S 0.3 0.2 546:56.46 systemd
5383 root 20 0 517524 129200 4576 S 0.3 6.9 38:08.60 rsyslogd

Options: ReplyQuote

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.