I am using spring-kafka RetryableTopic for non-blocking retries with a fixed BackOff and a single retry topic (https://docs.spring.io/spring-kafka/reference/html/#single-topic-fixed-delay-retries)
I noticed that I get RecordTooLargeException when retry-attempt is relatively high, and while checking the message I see that it contains the Kafka headers for all previous attempts, and some headers like kafka_exception-stacktrace they are quite heavy.
Why does it try to publish the retry message with the headers of the previous retries? I can not find any configuration for that. Can these headers somehow be manipulated to cut them before publishing?