Binlogging issues and concepts during restore using ndb_restore (Doc ID 1982400.1)

Last updated on MAY 25, 2015

Applies to:

MySQL Cluster - Version 7.2 and later
Information in this document applies to any platform.

Goal

Why using the --no-binlog option with ndb_restore, and restoring clusters 24GB (DataMemory), with memory usage around 60-80%, resulting in 10-100KB binary log files ? If --no-binlog option is used, would mysqld receive the corresponding events for the changes generated by ndb_restore? Or they would only receive the changes but ignore them?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms