Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[kafka-producer] Support setting max message size (jaegertracing#5263)
## Which problem is this PR solving? - Exposes MaxMessageBytes config mentioned in jaegertracing#1335 ## Description of the changes - Adds support to set MaxMessageBytes config on producer - Also setting a default which matches with [sarama](https://github.com/IBM/sarama/blob/main/config.go#L177) default unclear if we need to set that default explicitly from jaeger producer initialization ## How was this change tested? - Tested on our development jaeger cluster. After seeing below error we made following changes and built a new Image and verified that my changes fixed the issue ``` {"level":"error","ts":1550003610.8029132,"caller":"kafka/writer.go:59","msg":"kafka server: Message was too large, server rejected it to avoid allocation error.","stacktrace":"[github.com/jaegertracing/jaeger/plugin/storage/kafka.NewSpanWriter.func2](http://github.com/jaegertracing/jaeger/plugin/storage/kafka.NewSpanWriter.func2)\n\t/home/travis/gopath/src/github.com/jaegertracing/jaeger/plugin/storage/kafka/writer.go:59"} ``` ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` --------- Signed-off-by: Saketh kappala <[email protected]> Signed-off-by: Saketh <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
- Loading branch information