CPU mask for locking receiver threads to specific CPUs. This is specified as a hexadecimal bitmask. For example,  0x33  means that one CPU is used per receiver thread. An empty string is the default; setting ndb_recv_thread_cpu_mask  to this value removes any receiver thread locks previously set. This variable is global in scope. It can also be set at startup. NDB Cluster Configuration Files This represents the threshold for the number of epochs completely buffered in the event buffer, but not yet consumed by the binlog injector thread. When this degree of slippage (lag) is exceeded, an event buffer status message is reported, with  BUFFERED_EPOCHS_OVER_THRESHOLD  supplied as the reason (see Section 23.5.2.3, “Event Buffer Reporting in the Cluster Log” ). Slip is increased when an epoch is received from data nodes and buffered completely in the event buffer; it is decreased when an epoch is consumed by the binlog injector thread, it is reduced. Empty epochs are buffered and queued, and so included in this calculation only when this is enabled using the Ndb::setEventBufferQueueEmptyEpoch()  method from the NDB API. 4188 Command-Line Format --ndb-report-thresh-binlog-mem- usage=# System Variable ndb_report_thresh_binlog_mem_usage Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 10 Minimum Value 0 Command-Line Format --ndb-report-thresh-binlog-epoch- slip=# System Variable ndb_report_thresh_binlog_epoch_slip Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 10 Minimum Value 0 Maximum Value 256 System Variable ndb_recv_thread_cpu_mask Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Bitmap Default Value [empty] • ndb_report_thresh_binlog_epoch_slip • ndb_report_thresh_binlog_mem_usage