docs(clickpipes/mysql): FAQ for binlog event exceeding max_allowed_packet#6379
Merged
Conversation
…d_packet Document the MySQL error 1236 "log event entry exceeded max_allowed_packet" failure mode and its mitigations: increase max_allowed_packet on the source, resync the affected table, or exclude large columns from replication. The #binlog-event-exceeded-max-allowed-packet anchor is referenced by the ClickPipes notification for the NOTIFY_BINLOG_EVENT_EXCEEDED_MAX_ALLOWED_PACKET error class. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
ilidemi
reviewed
Jun 13, 2026
ilidemi
approved these changes
Jun 15, 2026
|
Docs PR opened: ClickHouse/mintlify-docs-dev#204 Added a MySQL ClickPipes FAQ entry explaining the max_allowed_packet binlog error and how to resolve it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The MySQL ClickPipe can fail with:
This happens when a single binlog event (one row change) is larger than the source server's
max_allowed_packet, aborting the binlog stream read. It's distinct from binlog corruption/purge and has its own mitigation.Change
Add a MySQL FAQ entry under
#binlog-event-exceeded-max-allowed-packetexplaining:BLOB/TEXT/JSONrows)max_allowed_packeton the source (up to1G)1GThis anchor is referenced by the new ClickPipes notification mitigation link for the
NOTIFY_BINLOG_EVENT_EXCEEDED_MAX_ALLOWED_PACKETerror class.Related
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only change to the MySQL ClickPipes FAQ; no runtime, auth, or data-path code is modified.
Overview
Adds a MySQL ClickPipes FAQ entry (
#binlog-event-exceeded-max-allowed-packet) for pipes that fail with ERROR 1236 when a binlog event exceeds the sourcemax_allowed_packet.The new section explains that CDC stops because the server cannot send oversized events (often from large
BLOB/TEXT/JSONrows), and documents fixes: raisemax_allowed_packeton the source (exampleSET GLOBALto 1 GiB plus persistentmy.cnf/parameter group config), and resync the pipe when a single row change is larger than 1G.This anchor is intended to back ClickPipes notification mitigation links for the
NOTIFY_BINLOG_EVENT_EXCEEDED_MAX_ALLOWED_PACKETerror class.Reviewed by Cursor Bugbot for commit 5880ab7. Bugbot is set up for automated code reviews on this repo. Configure here.