content_image/706825.jpg
• BUFFERED_EPOCHS_OVER_THRESHOLD : Whether the number of buffered epochs has exceeded the configured threshold. This number is the difference between the latest epoch that has been received in its entirety and the epoch that has most recently been consumed (in NDB API applications, this is done by calling nextEvent()  or nextEvent2() ). The report is generated every second until the number of buffered epochs goes below the threshold, which can be adjusted by setting the ndb_report_thresh_binlog_epoch_slip  server variable. You can also adjust the threshold in NDB API applications by calling setEventBufferQueueEmptyEpoch() . 

• PARTIALLY_DISCARDING : Event buffer memory is exhausted—that is, 100% of ndb_eventbuffer_max_alloc  has been used. Any partially buffered epoch is buffered to completion even is usage exceeds 100%, but any new epochs received are discarded. This means that a gap has occurred in the event stream. 

• COMPLETELY_DISCARDING : No epochs are buffered. 

• PARTIALLY_BUFFERING : The buffer free percentage following the gap has risen to the threshold, which can be set in the mysql  client using the ndb_eventbuffer_free_percent  server system variable or in NDB API applications by calling set_eventbuffer_free_percent() . New epochs are buffered. Epochs that could not be completed due to the gap are discarded. 

• COMPLETELY_BUFFERING : All epochs received are being buffered, which means that there is sufficient event buffer memory. The gap in the event stream has been closed. 

## 23.5.2.4 NDB Cluster: NDB Transporter Errors 

This section lists error codes, names, and messages that are written to the cluster log in the event of transporter errors. 

<img src='content_image/706825.jpg'>

