Commit e109b4b
Yevgeniy Miretskiy
changefeedccl: Increase message size limits for kafka sink.
Sarama library, used by kafka sink, limits the maximum message
sizes locally. When those limits are exceeded, sarama library
returns confusing error message which seems to imply that the remote
kafka server rejected the message, even though this rejection happened
locally:
`kafka server: Message was too large, server rejected it to avoid allocation error.`
This PR addresses the problem by increasing sarama limits to 2GB
(max int32).
An alternative approach was to extend `kafka_sink_config` to specify
maximum message size. However, this alternative is less desirable.
For one, the user supplied configuration can run afoul other limits
imposed by sarama library (e.g. `MaxRequestSize`), so more configuration
option must be added. In addition, this really exposes very low level
implementation details in the sarama library -- something that we
probably should not do.
Fixes #76258
Release Notes (enterprise change): Kafka sink supports larger messages,
up to 2GB in size.1 parent 3651e3c commit e109b4b
1 file changed
Lines changed: 13 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
| 17 | + | |
17 | 18 | | |
18 | 19 | | |
19 | 20 | | |
| |||
56 | 57 | | |
57 | 58 | | |
58 | 59 | | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
59 | 66 | | |
60 | 67 | | |
61 | 68 | | |
| |||
442 | 449 | | |
443 | 450 | | |
444 | 451 | | |
| 452 | + | |
| 453 | + | |
| 454 | + | |
| 455 | + | |
| 456 | + | |
| 457 | + | |
445 | 458 | | |
446 | 459 | | |
447 | 460 | | |
| |||
0 commit comments